Stats
Actions
Tags
From spec
Manage specification files. Use when creating, reading, updating, or listing spec files. Triggers on requests like "create spec", "update spec", "list specs", or "show spec status".
How this skill is triggered — by the user, by Claude, or both
Slash command
/spec:spec-file-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manages specification files in a configurable directory.
Manages specification files in a configurable directory.
Search for spec directory in this order:
specs/.specs/docs/specs/.dev-plans/If none found, ask user which directory to create.
Directory can be specified explicitly via command argument:
/spec:create-md docs/specifications
YYYY-MM-DD-{slug}.md
2025-01-22).mdExamples:
2025-01-22-user-auth.md2025-01-22-api-pagination.mdFlat structure. No subdirectories.
assets/spec-template.mdList all .md files in spec directory sorted by date (newest first).
Edit existing spec file in spec directory.
Remove spec file from spec directory.
See assets/spec-template.md for the specification file template.
npx claudepluginhub yaakaito/env --plugin specWrite 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".
Manages specification files with template-driven creation, duplicate detection, and conflict reporting. Automatically activates when creating or updating specs.
Manages feature specifications lifecycle: creates from requirements in draft/, tracks progress, moves to active (max 3) or completed folders. Use for planning, status checks, activation, or completion.