Loading...
Loading...
Found 15 Skills
Generate SDD requirements from RFCs/specs and quantitatively verify implementation conformance. spec draft → spec align → spec verify → automated validation loop with codex/claude. Operate spec-to-impl drift gates as CI checks.
Workflow navigation assistant that recommends next steps and optimizes documentation sequence through the SDD workflow
AI SDLC repository spec-driven development workflow. Use when an AI assistant receives a medium or large feature, refactor, API change, architecture change, provider integration change, or any request that must follow requirements, design, test cases, QA planning, tasks, implementation, and validation. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution.
Create Atomic Requirements (REQ) - Layer 7 artifact using REQ v3.0 format with 12 sections, SPEC-readiness scoring, and IMPL-readiness scoring
Investigates and analyzes an idea or codebase area before committing to changes. Pure research, no writes. Trigger: /sdd-explore <topic>, explore, investigate codebase, research feature, analyze before changing.
Use when the user wants to set up spec-driven development (OpenSpec + superpowers-bridge) in a project, or when initializing a new project that needs the SDD workflow. Idempotent. Runs the bundled scripts/run.sh.
Use when starting any development task beyond single-line fixes — classifies the request, detects current project phase, and routes to the right specification or execution tool
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Authors and consumes feature-level domain knowledge files in ai-context/features/. Reference guide for bounded-context business rules, invariants, integration points, and known gotchas.
Author or update the project's constitution — openspec/project.md — the non-negotiable principles, conventions, and constraints the Spec-Driven Development flow must honor. Modeled on GitHub Spec-Kit's /constitution. Run once per repo when onboarding SDD, or whenever the team's principles change. The sdd-feature-flow Analyze gate checks every spec against it.
Implements the corrections found by /project-audit. Reads audit-report.md as spec and executes each required action. Trigger: /project-fix, apply audit corrections, fix claude project.
Cria e mantém o TRD (Technical Requirements Document) em `docs/trd.md` — stack, arquitetura, requisitos não-funcionais, dependências externas, padrões e decisões globais do projeto. Também cria ADRs (Architecture Decision Records) no Modo Decision: registra uma decisão técnica em `docs/adrs/` e atualiza a seção Decisões Globais. O TRD é o contexto técnico consultado pelas skills do fluxo sdd (`sdd-especificar` em diante). Use ao criar um TRD, documentar a stack, registrar padrões de arquitetura, começar projeto novo sem TRD, quando a stack mudou, ou quando o `sdd-especificar` pedir contexto técnico por falta de `docs/trd.md` — mesmo sem usar o termo "TRD". Use o Modo Decision quando o usuário quiser "registrar uma decisão", "criar um ADR", ou disser "decidimos usar/trocar X por Y" — é decisão técnica/arquitetural, distinta de decisão de produto (que fica no PRD).