detailed-spec-writing

To convert fuzzy requirements into a precise spec, you provide an output file path and source references. The skill parses the inputs to identify independent capabilities and produces a SMARC-compliant PRD-formatted document at the specified location.

Yes, traceability and acceptance criteria are core to this spec writing process. The mechanism maps every identified feature directly to your source material references and explicitly outlines acceptance criteria to ensure testable specifications.

Decomposing high-level features into coding tasks requires a formal SMARC specification. The process parses source references to identify independent capabilities, enforces SMARC-compatibility, and outputs a structured PRD that planners can directly decompose.

The best way to surface ambiguities in requirements documentation is using a built-in self-review workflow. This mechanism automatically identifies gaps during spec generation, ensuring your formal PRD outputs remain precise and fully traceable to references.

Yes, you need to provide the task's output file path and any source references. The skill uses these inputs to parse independent capabilities, enforce SMARC-compatibility, and save the generated PRD-formatted spec at the specified location.

You should avoid SMARC-compliant specifications for tasks lacking clear source references or independent capabilities. Since the process enforces strict traceability and formal PRD formatting, it is not suited for informal planning or requirements that cannot be decomposed into testable criteria.