Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From devstefancho-skills
Manages specification files with template-driven creation, duplicate detection, and conflict reporting. Automatically activates when creating or updating specs.
npx claudepluginhub devstefancho/skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/devstefancho-skills:writing-specsgeneral-purposeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage spec files in `specs/` with conflict detection and a concise final report.
Write and manage spec files with search, conflict detection, and reporting. Use when user asks to create a spec, update a spec, write a spec, or mentions 스펙 생성, 스펙 업데이트, 스펙 작성, 스펙 만들어줘. Proactively trigger whenever the user's request involves specification documents, even if they don't explicitly say "spec".
Creates or updates SPEC.md documents from requirements, notes, or interview output, structuring into sections for goals, design, edge cases, security, testing, and success criteria. Use for feature specs.
Provides conventions for writing self-contained, implementation-ready spec documents. Distinguishes specs from docs; covers structure including data model, architecture, security, operations, scope, and deliverables.
Share bugs, ideas, or general feedback.
Manage spec files in specs/ with conflict detection and a concise final report.
specs/ at the project root. Filenames are lowercase-with-hyphens.specs/phase-N/NN-name.md — the convention writing-tasks consumes; using it makes the spec→task handoff zero-friction.
phase-N: 1-indexed milestone number, monotonically increasing across the project, never reset.NN: 2-digit index within the phase, starting at 01. Example: specs/phase-1/01-jwt-authentication.md.specs/{name}.md, specs/{subdir}/{name}.md) only when no writing-tasks integration is planned.Auto-pick phase + NN when the user does not specify:
Glob specs/phase-*/ — no phases → phase-1.phase-{N+1}.Glob specs/phase-N/*.md — new spec gets highest existing NN + 1, zero-padded.AskUserQuestion before creating a new phase.| Argument shape | Resolution |
|---|---|
brain-storm/**.md path | Read it. Summary / Motivation / Proposed Approach become the spec source; the idea title becomes the spec H1. |
| Any other markdown path | Read it; its content is the spec source. |
| Bare title or keyword | Glob brain-storm/**/*.md, match H1 (case-insensitive) then filename slug. One match → use it. Multiple → AskUserQuestion. Zero → treat as freestyle. |
| Freestyle text, or no argument | Use conversation context. Empty → ask via AskUserQuestion. |
From a brain-storm source: Summary seeds Purpose; Proposed Approach bullets seed Requirements (prune to 3-5 concrete items) and the prose Approach. Wireframe and Open Questions are NOT copied — list them under "Carried over" in the report.
Glob specs/**/*.md to list all spec files.Grep each keyword across the found specs.Glob).No specs/ directory yet → skip to Phase 3.
{path}. 업데이트할까요, 새로 생성할까요, 아니면 취소할까요?"All decisions go through AskUserQuestion.
specs/.Section limits (enforced, not suggested): Purpose 1-2 sentences, no bullets · Requirements 3-5 bullets, one concrete requirement each · Approach 2-5 sentences, no code · Verification 2-5 testable bullets.
For each outdated spec found in Phase 1: identify the broken references, propose specific updates, apply only after user confirmation. Never auto-modify.
Fill templates/report-template.md and output it as the final message: Action (Created/Updated), File (relative path), Title (spec H1), Search Results (each related/outdated spec, or "No related specs found"), Changes ("New spec created" or update summary), Next Steps (one actionable suggestion).
If AskUserQuestion is unavailable (auto mode, headless, scheduled), apply the defaults in non-interactive.md and echo every defaulted decision in the Phase 5 report.