feature-request

To turn a feature request into a requirements document and specification, provide the raw idea to generate a clear REQ document with scope, acceptance criteria, system-level basic SPEC, and module-level detail SPEC automatically.

Planning a multi-PR epic from a product change request involves routing the drafted requirements and design documents to an epic-author workflow, ensuring clean handoff for complex feature scopes.

Yes, you can capture architecture decision records (ADR) when drafting design specifications, integrating key technical decisions directly within the generated documentation for future traceability.

The feature planning workflow outputs documentation only, enforcing code-free specifications, requirements, and ADRs to separate design artifacts from implementation entirely.

You need detailed specifications versus a basic spec for new features when the product change requires module-level design beyond a simple note, triggering system-level and module-level specification drafting.

Single-PR scope differs from multi-PR epic triage in requirements planning by routing the generated documentation to a plan-author workflow for simple changes, while multi-PR scope triggers an epic-author workflow.