plan

To turn a PRD into an executable implementation plan, the Skill converts requirements into vertical tracer bullets that are demoable end-to-end. It applies dependency-aware slice ordering to sequence work correctly across schema, storage, routes, hooks, and components.

The best way to plan TDD strategies for feature slices is to define a test-first RED to GREEN cycle for each vertical slice. This keeps tests focused on behavior while ensuring executable, build-ready implementation phases.

Workflow-aware scoping adjusts planned feature implementation phases based on current workflow state or a single scope check question. This ensures the resulting plan aligns with existing project constraints before execution begins.

Yes, you can sequence a build order from schema to components because the Skill produces dependency-aware slice ordering. It breaks down vague conversation context or PRDs into the correct schema to storage to routes to hooks to components sequence.

A gated approval workflow is needed before feature execution to review the generated plan written to the .claude/plan.md file. This gate ensures the vertical slices and TDD strategy meet requirements before the build-feature command runs.