plan-to-features

To split a project plan into independently implementable features, the system analyzes your plan source, determines logical boundaries and ordering, and generates a sequenced set of self-contained feature documents. Each document is designed for isolated development.

The best way to generate feature documentation from a project plan is to use an automated workflow that locates your plan file, extracts functional boundaries, and outputs numbered feature docs into a predictable directory structure for cross-session development.

To prepare your project plan for feature document generation, place a markdown file named plan.md or PLAN.md in your project root. The system will automatically discover this file to analyze and split into ordered feature artifacts.

Yes, you can derive feature workflows without a plan file. If the system cannot locate a plan.md or PLAN.md in the project root, it will automatically derive the project plan context from your recent conversations to generate the feature directory.

Generated feature docs are stored in a dedicated /.agent-features/ directory at your project root. The system uses deterministic, numbered file naming like 01-... and 02-... to ensure predictable sequencing and self-contained artifacts for implementation.

Yes, plan-to-features works for cross-session project management by creating ordered, self-contained feature docs that guide implementation across different sessions. It outputs a progress reporting summary to track the scope of created artifacts.