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 Save to: `docs/superpowers/specs/<STORY-KEY>.md` — the Jira story key is the entire filename (e.g. `docs/superpowers/specs/CER-2037.md`). The key is globally unique, so any agent can derive this path without a Jira lookup. Commit on branch `spec/<STORY-KEY>`. Raise PR titled `docs(spec): <STORY-KEY> <story summary>`. After the PR is merged, comment on the story as a human-readable breadcrumb: ```bash acli jira workitem comment add <STORY-KEY> \ --body "Spec: docs/superpowers/specs/<STORY-KEY>.md | PR: <PR_URL>" ``` This comment is for human reference only — other agents derive the path from the story key directly, not from this comment. **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 ````markdown # [Feature Name] — Technical Spec **Story:** [JIRA-KEY — link or key] **Feature:** [link to