plan

Converts a feature spec into a phased, TDD-first implementation plan with paste-ready prompts.

Updated May 26, 2026
One-click install
npx skills add https://github.com/robot-denny/ai-sketchlab --skill plan-robot-denny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/robot-denny/ai-sketchlab/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/robot-denny/ai-sketchlab --skill plan-robot-denny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into an ordered, executable implementation plan is error-prone: steps get batched, tests get written after code, and key design decisions are lost between sessions. This Skill structures that translation so each step is independently completable in a fresh context window. ## Core Features & Use Cases - Spec-to-plan conversion: Resolves a spec file path, a bare slug, or a free-text description into a saved plan file with context, key decisions, and sequenced steps. - TDD-first sequencing: Orders schema before logic and tests before implementation, with RED/GREEN expectations and manual verification checkpoints per step. - Work-type-aware completion: Branches the final step on work type (new-capability, change-to, fix-infra) so durable behavior is recorded in the right artifact — a feature doc, an updated capability doc, or a runbook. - Use Case: After drafting a spec for a new content-editing feature, run the plan skill with the spec slug to produce a step-by-step plan where each step carries a paste-ready prompt for a fresh implementation session. ## Quick Start Ask the AI to create an implementation plan from your spec file, for example by providing the path to the spec or its slug.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a feature spec into an implementation plan?

Provide the spec file path, its slug, or a short description as input. The skill resolves the spec, reads the codebase for existing patterns, and saves a plan file with sequenced steps, key decisions, and a paste-ready prompt per step.

How does the plan skill enforce test-driven development?

Each step that introduces testable behavior writes the test first and confirms it fails (RED) before implementing (GREEN). Test-writing and implementation stay in the same step unless the implementation is large, and multiple behaviors are never batched into one test step.

What input formats does the plan skill accept?

It accepts three forms: a file path containing a slash or ending in .md, a bare kebab-case slug that resolves to a saved spec, or free-text description. Slugs that do not resolve to an existing spec stop the process rather than inventing one.

What happens after the implementation steps in the plan?

The final step records durable behavior based on work type: new capabilities verify a feature doc, changes fold observable behavior into an existing capability doc, and infrastructure fixes produce a runbook under docs/ instead of a feature doc.

When should I not use a structured implementation plan?

Very small, single-file changes with no testable behavior gain little from phased planning. The skill is designed for multi-step work where steps must be independently completable and design decisions need to persist across sessions.