Stats
Actions
Tags
From dev-team-kit-fv
Transforms a feature idea or requirement into a formal specification with user stories, numbered acceptance criteria, priority, and risks.
How this command is triggered — by the user, by Claude, or both
Slash command
/dev-team-kit-fv:specThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /spec — Especificação de Feature **Objetivo:** Transformar uma ideia ou requisito em especificação formal com critérios de aceitação claros. **Skill ativada:** 01 — PO (Feature Spec) **Input esperado:** Descrição da feature, contexto de negócio, público-alvo. **Output esperado:** Spec com user stories, critérios de aceitação numerados, prioridade e riscos. **Policies relevantes:** - `policies/execution.md` — escopo e qualidade - `policies/confusion-management.md` — STOP-NAME-OPTIONS-WAIT se requisito ambíguo - `policies/prd-validation.md` — 13 checks fixos sobre qualidade da spec - `...
Objetivo: Transformar uma ideia ou requisito em especificação formal com critérios de aceitação claros.
Skill ativada: 01 — PO (Feature Spec)
Input esperado: Descrição da feature, contexto de negócio, público-alvo.
Output esperado: Spec com user stories, critérios de aceitação numerados, prioridade e riscos.
Policies relevantes:
policies/execution.md — escopo e qualidadepolicies/confusion-management.md — STOP-NAME-OPTIONS-WAIT se requisito ambíguopolicies/prd-validation.md — 13 checks fixos sobre qualidade da specpolicies/constitution.md — se memory/constitution.md existir, spec deve respeitar os 5 eixosHandoff recomendado:
/checklist <spec_path> para gerar checklist contextual ("unit tests for English")/plan/build (se já houver issues): rodar /analyze para cross-artifact consistencyUso: /spec [descrição da feature ou contexto]
npx claudepluginhub felvieira/claude-skills-fv --plugin dev-team-kit-fv/specDrafts or refines a Phase 0 feature specification with requirements and acceptance criteria, writing output to a plans file.
/specsGenerates collaborative specifications for a feature, producing Intent, BDD scenarios, architecture notes, and acceptance criteria.
/specGenerates a feature spec via interactive Q&A on problem, users, scope, edges; fills template; runs Gate 1 checklist; saves to .planning/specs/<feature>.md
/specifyTransforms project briefs into structured specifications with functional requirements, acceptance criteria, and testable requirements. Generates docs/specification.md and optionally auto-proceeds to planning.
/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/specAuthors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.