cpm:spec

Create structured requirements and architecture specifications through guided conversation.

Updated Oct 11, 2025

Search Tags:#workflow #planning #architecture #documentation #specification #requirements #adr

Ready to run

npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cpm:spec
Source: https://github.com/ninthspace/claude-code-marketplace/tree/main/cpm/skills/spec
Command: npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines building structured requirements and architecture specifications through guided conversation, ensuring input sources, ADR considerations, and scope boundaries are captured consistently.

Core Features & Use Cases

Guided input resolution from briefs, plans, or user prompts.
Section-by-section gating with AskUserQuestion to ensure progress is incremental.
ADR and library context integration to reference existing decisions and standards.
Progress tracking via a persistent plan file for compaction resilience.

Quick Start

Provide a problem brief or description to begin assembling a guided spec, and we will prompt you through each section one by one.

Frequently Asked Questions about cpm:spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create structured requirements and architecture specifications from a problem brief?▼

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.

How does guided conversation work for drafting software specifications?▼

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.

Can I use existing ADRs and library references when building a product spec?▼

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.

What is the best way to manage scope boundaries and input resolution for architecture documentation?▼

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.

Does this specification workflow support enterprise product teams?▼

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.

Why use a persistent plan file when assembling architecture specifications?▼

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.