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-pluginThis skill is limited to using the following tools:
Manages spec files in `specs/` directory with conflict detection and concise reporting.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
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.