plan

Interview users to write feature specs and TDD task breakdowns.

1|Updated Jan 27, 2026

Search Tags:#tdd #requirements #interview #backlog #plan #spec-writing

Ready to run

npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill plan-joaovsales

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Joaovsales/coding-agent-workflow/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill plan-joaovsales

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview the user to extract clear feature requirements, then generate a formal spec and a TDD task plan to prevent scope creep and rework.

Core Features & Use Cases

Structured user interviews to capture goals, constraints, and acceptance criteria.
Persist a formal spec to specs/<feature-name>.md.
Create a concrete Plan in tasks/todo.md with a ready-to-run "## Plan: ..." block.
Gate the workflow with a save-before-use policy and prepare for a smooth TDD handoff.

Quick Start

Ask the user targeted questions to define the feature, then save the spec and plan to their project workspace.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I write a feature spec before coding to prevent scope creep?▼

To write a feature spec and prevent scope creep, this tool conducts structured user interviews to capture goals and constraints, then persists a formal spec document to your project workspace.

What is the best way to generate a TDD task breakdown from requirements?▼

Generating a TDD task breakdown from requirements involves extracting acceptance criteria during an interview, then creating a concrete Plan block in tasks/todo.md for a smooth TDD handoff.

How do you conduct a requirements interview for a non-trivial software feature?▼

Conducting a requirements interview for a non-trivial feature requires asking targeted questions to define the scope, which then produces a formal spec and a ready-to-run task plan.

Do I need a backlog before starting spec-writing and TDD planning?▼

You do not need a formal backlog before spec-writing; the process interviews you directly to capture feature requirements and generates the TDD plan to gate the workflow and prevent rework.

Where are feature specs and TDD plans saved in the project workspace?▼

Feature specs are saved to specs/<feature-name>.md, and the TDD plan is created in tasks/todo.md, enforcing a save-before-use policy to prepare for implementation.