writing-specslisted

# writing-specs — Technical Spec **Core principle:** A spec says WHAT to build — not HOW to implement it line by line. Every section must be concrete enough that an implementation agent can execute without asking questions. **Announce at start:** "I'm using the writing-specs skill to produce this spec." ## When to Use - Before any implementation planning (`writing-plans` consumes this output) - When given a Jira story key or a product feature doc - When requirements exist but no technical design has been written ## Output File ```text save_path := docs/superpowers/specs/<STORY-KEY>.md # story key is globally unique -> any agent derives this path with no Jira lookup, e.g. docs/superpowers/specs/CER-2037.md branch := spec/<STORY-KEY> pr_title := docs(spec): <STORY-KEY> <story summary> PR merged -> post breadcrumb comment on the story # human reference only; other agents still derive save_path from the story key, not from this comment ``` ```bash bash ${CLAUDE_PLUGIN_ROOT}/scripts/jira-site-guard.sh || exit 1 acli jira workitem comment create --key <STORY-KEY> \ --body "Spec: docs/superpowers/specs/<STORY-KEY>.md | PR: <PR_URL>" ``` **Guard:** If you did not successfully fetch the Jira ticket before calling this skill, STOP and return to fetch it first. Never generate spec content from repository files alone. --- ## Spec Template Artifact encoding contract: unpadded tables, no section dropped, one-line N/A, verbatim contracts, rationale as annotation, prose < 10