Stats
Actions
Available In
Tags
Plugin
specture
Spec-Driven Development framework for AI-assisted software development
What's Inside
Agents6
architecture-validator
/AGENT
Validates that a plan, spec, or architecture document complies with the project's locked stack and conventions (`.specture/`) and with all Accepted ADRs. Returns APPROVED or REJECTED with specific violations. Does NOT propose fixes.
code-reviewer
/AGENT
Independent reviewer for implemented code. Performs a unified review in one pass across four core dimensions (spec compliance, architecture compliance, code quality, TDD honesty) plus two optional ones (stack idiomaticity via Context7, and frontend fidelity for UI epics — token/contract/a11y adherence). Returns APPROVED, REJECTED_MINOR, or REJECTED_MAJOR with concrete fixes. Does NOT modify code.
implementer
/AGENT
Writes minimal production code to make a set of failing tests pass, following the project's stack, conventions, and ADRs. Receives the spec, the tests, and the relevant existing source files — operates with restricted context to avoid drift.
specture-router
/AGENT
Use ONLY when explicitly invoked via `/specture:start`, or when the user asks to start/continue Specture work ("continuemos con el roadmap", "sigamos", "inicia el proyecto"). Inspects the current state of the user's project and routes to the correct phase skill. NOT activated automatically — Specture routing is opt-in since v1.5.0.
tdd-test-writer
/AGENT
Writes failing tests for a spec following TDD RED-phase discipline. Receives ONLY the spec, business rules, and stack/test framework — never sees existing implementation. Tests must be based on requirements, not on what the code currently does.
Skills16
architecture
/architecture
Use when business requirements exist but no architecture or roadmap, when the user says "diseñemos la arquitectura", "generemos el roadmap", "planifiquemos", or whenever `docs/04-roadmap/ROADMAP.md` does not yet exist. Produces a tech-agnostic architecture document, an API contract (OpenAPI + readable companion) as the single source of truth for the backend/frontend interface, and a milestone/epic ROADMAP — all validated by the architecture-validator agent.
audit-knowledge
/audit-knowledge
Use periodically (every 1-3 months in mature projects) or whenever the docs-index seems out of sync with the actual repo. Detects entries pointing to missing files, stale `last_verified` dates, duplicate concepts, and docs in the source-of-truth dir that are NOT in the index. Reports drift but does NOT auto-fix — proposes actions for the user to confirm.
build
/build
Use when `docs/04-roadmap/ROADMAP.md` exists and contains epics marked `[ ]` (pending) or `[/]` (in progress), or when the user says "construyamos", "sigamos con el roadmap", "implementemos el siguiente epic". Orchestrates a strict per-epic loop: spec → architecture validation → tests → implementation → review → verification → mark complete. Dispatches specialized agents (tdd-test-writer, implementer or ux-implementer for UI, code-reviewer). Frontend epics add a design-system-first order and a human visual-approval gate.
contract-sync-audit
/contract-sync-audit
Use on an existing project where the frontend and backend are out of sync — the frontend calls URLs the backend doesn't expose, expects response shapes the backend doesn't return, or uses different paths/methods. Statically extracts backend routes and frontend API calls, diffs them, and emits a reconciliation report against a canonical source (an existing API contract, or one chosen side). Does NOT auto-fix — it reports and proposes, then routes to build/new-feature/debug. Also use before copying a design handoff into a codebase whose API is already drifting.
debug
/debug
Use the moment any test fails twice, when a build breaks unexpectedly, when the code-reviewer rejects code, when the implementer reports BLOCKED, when the user reports a bug, or when you find yourself "trying things". Stops guess-and-check loops. Forces root-cause investigation with a physical debug log artifact before any fix is attempted.
Stats
Version1.7.1
LanguageJavaScript
Stars0
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Uses power tools
Uses Bash, Write, or Edit tools
Tags
Categories
