plan

Convert user stories into implementation plans with tasks, file changes, and dependencies.

5|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/jstoup111/ai-conductor --skill plan-jstoup111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/plan
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill plan-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires verify-claims, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating a technical implementation plan for user stories, streamlining the translation of stories into actionable tasks and ensuring a cohesive, manageable development workflow.

Core Features & Use Cases

  • Technical Plan Creation: Automatically transforms user stories into a detailed plan with step-by-step tasks, file changes, and dependencies.
  • Task Granularity: Breaks stories down into tasks at a 2-5 minute work estimate to facilitate Time-Driven Development (TDD).
  • Precondition Validation: Ensures that all necessary preconditions are met before proceeding with planning, including validated story paths and clean conflict checks.

Quick Start

Use the plan skill to create an implementation plan for your new feature based on your user stories in '.docs/stories/'.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert user stories into a technical implementation plan?

Task breakdown for Time-Driven Development involves splitting user stories into tasks estimated at 2-5 minutes of work each. This granularity ensures a manageable development workflow and facilitates efficient coding and testing cycles.

What preconditions are required for technical planning from user stories?

Technical planning requires validated story paths within '.docs/stories/' and clean conflict checks. The process validates these preconditions before automatically generating plan files and architecture diagrams in '.docs/plans/'.

Does user story planning require any specific verification scripts?

User story planning requires the 'verify-claims' dependency to ensure preconditions are met. This validation step guarantees that story artifacts are properly structured before generating the implementation plan.

What's the best way to structure tasks for a development workflow?

The best way to structure tasks for a development workflow is to break them down into 2-5 minute work estimates. This approach supports Time-Driven Development (TDD) by creating precise, actionable steps with clear file changes and dependencies.

Where are implementation plan files and architecture diagrams stored?

Implementation plan files and architecture diagrams are stored in the '.docs/plans/' directory. Related reference files are simultaneously output to '.docs/references/' during the automated planning process.