specture

Plugin specture from marketplace specture in FerEscobarDev/Specture. Commands read from the repo's manifest — 18 days ago.

Skills (17)

• 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 + readab

• audit-knowledge

  Alias of `knowledge` in AUDIT mode. Use when the user invokes `/specture:audit-knowledge` or asks to audit the docs-index for drift (orphans, stale entries, duplicates, uncovered docs). Backward-compat alias — the real procedure lives in `skills/knowledge/SKILL.md`.

• compliance-review

  Use when a milestone closes in the build (Step 8.7 calls it), when the build queue drains with a compliance report waiting for triage, when the user asks to check code against ALL the project rules — "revisión de cumplimiento", "revisá el milestone N contra las reglas", "qué reglas incumple lo que c

• 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 reco

• 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

• discover

  Use when the user wants to start a new project, lift requirements, "levantar requerimientos", "iniciar un proyecto nuevo", "definir el negocio", or whenever `docs/01-requirements/business_requirements.md` does not yet exist. Also runs in brand-only mode on `/specture:discover --marca`, when requirem

• doctor

  Use when the user asks to check, lint or repair the project''s Specture structure ("revisá el proyecto", "está todo en orden", "actualizá la config de specture"), right after upgrading the plugin, when `start` reports pending migrations, or on `/specture:doctor [check|migrate|sync]`. Read-only by de

• knowledge

  Use to keep the project''s knowledge healthy. Three modes: `capture` (alias `/specture:learn`) — after an epic closes, a root cause is confirmed or on demand, turn session discoveries into durable artifacts (docs-index entries, ADR drafts, rules.yml entries, conventions patches), max 3 drafts with g

• learn

  Alias of `knowledge` in CAPTURE mode. Use when the user invokes `/specture:learn` or asks to capture session learnings (post-epic, post-debug, on demand, or `--teach <concept>`). Backward-compat alias — the real procedure lives in `skills/knowledge/SKILL.md`.

• modernize

  Use when the user wants to upgrade a technology version (e.g. .NET 8 → .NET 10, Node 18 → 22, Angular 6 → Angular 20) or migrate to a different technology stack (e.g. AngularJS → React, Express → NestJS, Vue 2 → Vue 3). Performs gap analysis, writes characterization tests BEFORE touching any code, a

• new-feature

  Use when the user asks to add functionality not present in the original ROADMAP — phrases like "quiero agregar X", "necesito una nueva funcionalidad", "ahora también queremos…". Performs Impact Ripple Analysis against existing specs, updates the ROADMAP with the new milestone/epic, and routes to the

• setup-docs-bridge

  Use when the user has an existing project (mode Adopt) that already contains a folder with substantial preexisting documentation (`docs/`, `Documentation/`, `wiki/`, `*.Docs/`, etc. with ≥10 .md files), and Specture must integrate that documentation without duplicating it. Generates `.specture/docs-

• setup

  Use when the user says "configura el proyecto", "setup", "instala Specture", "ajusta las reglas", or when `.specture/stack.yml` does not exist in the project root. Initializes the Specture configuration in three modes (bootstrap for empty projects, adopt for existing codebases, reconfigure for alrea

• start

  Use at the start of every conversation under Specture, when the user says "continue", "sigamos", "continuemos con el roadmap", asks to resume work, or whenever the current phase of the project is unclear. Detects project state and routes to the correct phase skill.

• ux-design

  Use when the project has a frontend (`stack.yml.frontend.framework` is set and not `none`) and `docs/03-ux-ui/navigation_map.md` or `design_system.md` is missing. Also use when the user says "diseñemos la UI", "el diseño ya está en Claude Design", or asks to start the frontend. Forces the aesthetic

• verify

  Use before claiming any work is "done", "completed", "fixed", "passing", or "ready". Use before committing, before creating PRs, before marking a task or epic complete in ROADMAP, before delegating downstream. Forces fresh execution of the relevant verification command and reading of its output befo

• write-skill

  Use when the user wants to create a new Specture skill, modify an existing one, write a custom agent, or extend the framework. Enforces TDD-for-documentation: every skill must be tested with pressure scenarios before it ships.

Hooks (2)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/pre-tool-use-tdd-gate.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/pre-tool-use-wait-gate.js"

Similar plugins