planning

Plan feature work with TDD and LOG-based progress tracking.

2|Updated Mar 19, 2024
One-click install
npx skills add https://github.com/yankeeinlondon/typed-tester --skill planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/yankeeinlondon/typed-tester/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/yankeeinlondon/typed-tester --skill planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires simple-git, and includes scripts (resource) components.

What problem does it solve?

This Skill formalizes and streamlines the development workflow for new features, ensuring a consistent, Test-Driven Development (TDD) approach. It helps developers plan effectively, track progress, and integrate both runtime and type testing to build robust TypeScript applications, reducing ad-hoc processes and potential regressions.

Core Features & Use Cases:

  • Structured TDD Workflow: Guides you through a comprehensive 5-step process (Snapshot, Log, Write Tests, Implement, Close Out) for predictable and high-quality feature development.
  • Comprehensive Testing Guidance: Provides detailed instructions on when and how to apply both runtime and type tests, including common pitfalls and best practices specific to TypeScript.
  • Automated State Tracking: Utilizes a script to capture the repository's Git and test state at the beginning of each development phase, establishing clear baselines and aiding in debugging.
  • Use Case: When you're about to start a new feature, activate this Skill to automatically generate a structured plan, capture your current project state, and receive step-by-step guidance through a TDD cycle, ensuring your work is well-tested and documented.

Quick Start:

To capture the initial state for a new plan phase (e.g., "my-new-feature", phase 1):

bun run .claude/skills/planning/scripts/start-position.ts my-new-feature 1

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Test-Driven Development workflow for TypeScript features?▼

Test-Driven Development enforces writing tests before implementation to catch regressions early. This Skill guides you through a structured 5-step TDD cycle—Snapshot, Log, Write Tests, Implement, Close Out—using Vitest for runtime tests and TypeScript's type system for type tests, ensuring robust feature delivery.

Can I use TDD with TypeScript and track progress across multiple development phases?▼

Yes. This Skill captures your Git and test state at each phase, maintains a LOG file for progress tracking, and prescribes Vitest and pnpm tooling. You run `start-position.ts` with a feature name and phase number to establish baselines and move systematically through development.

What's the best way to plan feature work with mandatory runtime and type tests?▼

Feature planning works best when you scope work upfront, define test strategy for both runtime and type coverage, and track progress in a LOG file alongside Git snapshots. This Skill automates that workflow, enforcing TDD discipline and reducing ad-hoc processes for TypeScript projects.

How do runtime tests and type tests work together in TypeScript development?▼

Runtime tests verify behavior at execution time; type tests catch errors at compile time. Together they eliminate categories of bugs. This Skill provides detailed guidance on when and how to apply each, including TypeScript-specific pitfalls, so your feature work is protected at both layers.

Do I need Git integration to use this planning workflow?▼

Yes. This Skill uses simple-git to capture repository state and establish clear baselines at each development phase. Git integration enables automated state tracking and aids debugging when regressions occur.

What happens if I skip type testing during feature development?▼

Skipping type tests misses compile-time errors that TypeScript can catch—the Skill mandates both runtime and type tests to prevent that gap. Incomplete testing increases regression risk and defeats the TDD discipline the workflow enforces.