cpm:spec

You can create structured requirements and architecture specifications by providing a problem brief to initiate a guided conversation, which then prompts you through each section one by one to ensure consistent scope capture.

Guided conversation drafts software specifications by applying section-by-section gating with AskUserQuestion, ensuring progress is incremental and tracking it via a persistent plan file for compaction resilience.

Yes, you can use existing ADRs and library references when building a product spec. The process integrates architectural decision records and library context to reference established decisions and standards.

The best way to manage scope boundaries and input resolution for architecture documentation is through facilitated input resolution from briefs, plans, or prompts, ensuring all source considerations are captured consistently.

Yes, this specification workflow supports enterprise product teams. It applies to product teams drafting specs from problem briefs, ADRs, and library references across startup to enterprise contexts.

You use a persistent plan file when assembling architecture specifications to enable progress tracking. This ensures compaction resilience, allowing the guided specification process to maintain state across sessions.