systematic-planning

To turn a vague feature request into an actionable plan, define the feature and run the planning workflow. It generates a structured markdown document translating ambiguous requirements into business specifications, technical architecture, and implementation tasks.

The best way to structure implementation tasks for multi-component features is using a phase-based approach. This workflow separates business specification, technical architecture, and task phases, assigning files and acceptance criteria to each component like backend and infrastructure.

You create a planning document with business specifications and technical architecture by defining your feature request and triggering the planning workflow. It outputs a structured markdown file covering business specs, architecture, and implementation tasks.

Generated markdown planning documents are saved to .claude/plans/[feature-name].md for traceability and handoff. This standardizes storage so teams can easily locate the business specification, technical architecture, and implementation tasks for any feature.

Yes, you need a frontmatter-driven SKILL.md file with a name and description to start planning a multi-component software feature. This provides the necessary input for the workflow to generate the structured markdown plan and implementation tasks.

Yes, you can use this workflow to plan backend, bot interfaces, and infrastructure components together. It operates across business specification, technical architecture, and implementation task phases specifically designed for multi-component feature planning.