Help us improve
Share bugs, ideas, or general feedback.
From writing-specs-plugin
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".
npx claudepluginhub devstefancho/claude-plugins --plugin writing-specs-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/writing-specs-plugin:writing-specsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manages spec files in `specs/` directory with conflict detection and concise reporting.
Manages specification files with template-driven creation, duplicate detection, and conflict reporting. Automatically activates when creating or updating specs.
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.
Manages spec files in specs/ directory with conflict detection and concise reporting.
specs/ at the project rootspecs/{name}.md or specs/{subdir}/{name}.mdspecs/api/auth.md is OK, specs/api/v2/auth.md is NOT)jwt-authentication.md)Before any create or update operation, search for existing specs:
Glob specs/**/*.md to list all existing spec filesGrep for each keyword across all found spec filesGlob)If no specs/ directory exists yet, skip search and proceed to Phase 3.
Based on search results:
{path}. 업데이트할까요, 새로 생성할까요, 아니면 취소할까요?"Use AskUserQuestion for all user decisions.
specs/Section constraints (enforced, not suggested):
If outdated specs were found in Phase 1:
Read the report template and fill it in: templates/report-template.md
Output the completed report as the final message. This is how the user sees what happened.