specbox-engine

Generate technical implementation plans with UI component analysis, agent mapping, and Stitch design generation. Use when the user says "plan feature", "create plan", "technical plan", "analyze for implementation", or references planning before coding. Reads PRDs from Plane/Trello.

Configure complete visual identity for a project before development. Use when the user says "visual setup", "setup design", "configure brand", "design system", "visual identity", "brand kit", or wants to set up Stitch + VEG + brand tokens before running /plan.

Audits, cleans, and releases a new SpecBox Engine version. Checks for residual code, updates ENGINE_VERSION.yaml, CLAUDE.md, changelog, and pushes to remote. Use when the user says "release", "bump version", "new version", "cut release", "audit and release", "sube version", "prepara release".

Cambia el backend de tracking de un proyecto entre los 4 (FreeForm / Trello / Plane / Native) de forma guiada y sin pérdida de avance. Migra US/UC/AC/comments/ estado al destino, actualiza atómicamente los 3 lugares de verdad, y ofrece regenerar evidencias. Use when the user says "switch backend", "cambiar backend", "migrar de FreeForm a Trello/Plane/Native", "mover el tracking a", "change tracking backend".

Autonomous implementation from a plan file. Creates feature branch, implements all phases, generates Stitch designs if needed, converts designs to code, runs QA validation, and creates GitHub PR. Use when the user says "implement plan", "execute plan", "autopilot", or references implementing a previously created plan.

ISO/IEC 25010 (SQuaRE) quality audit on-demand for onboarded projects. Use when the user says "audit project", "quality audit", "ISO 25010", "SQuaRE audit", "audita el proyecto", or wants a comprehensive quality report across 8 characteristics with PDF + JSON evidence.

Capture developer testing feedback as structured evidence and GitHub issues. Use when the user says "report feedback", "found a bug", "this doesn't work", "feedback on feature", "AC-XX is wrong", or reports an issue found during manual testing. Links feedback to acceptance criteria and blocks merge if unresolved.

Product Discovery ligero (15-30 min) antes de /prd. Guía conversacional en 3 fases (ICP identification, JTBD extraction, validation gate) que produce doc/discovery/<feature>/icp_jtbd.md y, en modo bootstrap, también doc/app/app_market.md. Use when the user says "discovery", "framing", "antes de PRD", "definir ICP", "definir JTBD", o ejecuta /discovery <feature_name>. Skill v6.0.0 — "Discovery Foundations".

Persiste el estado fino de la sesión actual a `.quality/handoff.md` y a Engram como observación estructurada. Use when the user says "handoff", "save state", "guarda contexto", "persistir sesión", "voy a hacer compactación", or before `/clear`. CRITICAL: si Claude está por proponer compactación o el usuario menciona "compactar"/"nueva sesión", invocar este skill ANTES.

Standalone acceptance check — validates AC from PRD against code without full /implement pipeline. Use when the user says "check acceptance", "validate AC", "verify acceptance", "acceptance gate", or needs to verify acceptance criteria for a PR or external contribution.

Verify, repair, review, or rebuild the canonical project documents `doc/app/app_prd.md` and `doc/app/app_spec.md`. Runs the four subcommands of the v5.29.0 sync layer: --check (CI-friendly drift report), --repair (interactive auto-zone reconciliation), --review (human-mediated case-by-case), --rebuild-from-tracking (emergency regenerate). Use when the user says "app sync", "sync app docs", "check app drift", "reparar app docs", "rebuild canonical docs", or after an `app-docs-sync-guard` warning to act on the drift.

Generate structured Product Requirements Documents from feature descriptions. Use when the user says "create PRD", "new feature", "write requirements", "define feature", or references creating specifications for implementation. Supports Trello (spec-driven) and Plane work item creation.

Interactive tutorial — guides new developers through the full SpecBox Engine pipeline with a demo project. Use when the user says "quickstart", "tutorial", "getting started", "learn engine", or needs onboarding to the engine.

Initialize or refresh the canonical project documents `doc/app/app_prd.md` and `doc/app/app_spec.md`. These are the single source of truth that `/prd`, `/plan`, and `/visual-setup` consult before asking the user questions whose answers can be inherited from the project. Idempotent: safe to run multiple times. Detects state (empty / tracking-populated / app-already-exists) and adapts behavior accordingly. Use when the user says "app init", "init app docs", "create canonical docs", "setup project canon", or after a fresh clone before running `/prd`.

Review and resolve entries in `doc/app/decisions_queue.md` — the deferred decisions queue introduced in v5.29.0. Lists pending entries from one or many projects, lets the user confirm / adjust / revert each, and moves resolved ones to the historical section. Use when the user says "queue review", "review queue", "revisar cola", "resolver pendientes", or wants to batch-process decisions accumulated by the autopilot in `equilibrado` / `agresivo` modes when `autopilot.queue_enabled=true`.

Rotates the active Stripe account of a SpecBox project safely. Wraps the switch_stripe_account MCP tool with a UX layer: shows current alias store, asks for from/to, runs dry-run, formats the plan in Markdown, asks for literal confirmation, executes, and surfaces the rollback runbook if something fails. Supports both account_mode='standard' (SaaS, e-commerce) and 'connect' (marketplace). Use when the user says "switch stripe account", "rotar cuenta stripe", "cambiar cuenta stripe", "cambiar de cuenta de stripe", "rotate stripe account", "stripe credentials rotation".

Scaffolds a Stripe **Standard account** integration (no Connect) in Supabase + React/Flutter projects. Generates US-STRIPE-CHECKOUT with up to 12 UCs covering the 4 canonical billing modalities (single subscription, tiered subscriptions, metered billing, one-shot checkout) in the project's spec backend, backend Edge Functions + SQL migrations with RLS, frontend templates with Payment Element/Sheet + Apple/Google Pay + Express Checkout, Stitch designs (if VEG configured), reuses the stripe-safety-guard hook, events catalog, and wires the official Stripe MCP. Use when the user says "stripe standard", "stripe sin connect", "subscriptions saas", "checkout one-shot", "billing saas", "monta pagos saas", "monta pagos e-commerce". v1 scope: Supabase only, the 4 modalities are flags so the user opts in.

Scaffolds a Stripe Connect marketplace integration (Express + Direct charges + subscriptions embedded) in Supabase + React/Flutter projects. Generates US-SPONSORSHIP with 12 UCs in the project's spec backend, backend Edge Functions + SQL migrations with RLS, frontend templates with Payment Element/Sheet + Apple/Google Pay + Express Checkout, Stitch designs (if VEG configured), stripe-safety-guard hook, events catalog, and wires the official Stripe MCP. Use when the user says "stripe connect", "marketplace billing", "integrar pagos marketplace", "implementar pagos stripe", "monta pagos marketplace". v1 scope: Supabase only, Connect Express only, Direct charges only, subscriptions only.

Systematic manual testing with live bug resolution and stakeholder evidence. Use when the user says "manual test", "pruebas manuales", "test plan", "monta el sistema de pruebas manual", "testear la app", or wants to validate features interactively before a demo or release. The user provides screenshots, the agent diagnoses and fixes bugs in real-time.

Retroactive compliance check for Stitch designs. Scans all UCs with screens and reports which have Stitch HTML designs and which don't. Use when the user says "check designs", "design compliance", "verify designs", "stitch status", or wants to audit design-to-code traceability.

SpecBox Engine compliance audit — checks version alignment, hooks, settings, quality infra, skills, and spec-driven compliance. Auto-fixes gaps and generates remediation plan.

Audit, score, and optimize the multi-agent system. Analyzes documentation sync, validation strategy, model optimization, team coordination, and Agent Teams readiness. Use when the user says "audit agents", "optimize system", "agent score", "check agent health", or references improving the agentic setup.

Adaptive quality gates with auto-discovered baseline and auditable evidence. Use when the user says "check quality", "run gates", "quality report", "coverage check", or before creating a PR to validate code quality. Policies: zero-tolerance lint, ratchet coverage, no-regression tests.

Scan project widget/component structure and generate UI mapping file. Use when the user says "scan UI", "map components", "adapt UI", "detect widgets", or needs to understand the project's UI inventory before planning a feature.

Read-only codebase exploration and analysis. Use when the user asks "analyze codebase", "explore code", "what does this project do", "find files related to", "understand architecture", or needs to research the codebase before making changes. Cannot modify any files.