Given a scope prose + mode, globs docs/decisions/.md, reads only the frontmatter of each candidate, applies a per-mode candidate-pool filter, and returns a ranked shortlist of decisions docs semantically correlated with the scope. Used by plan-context in both phase mode (pool = ad-hoc docs with relatedphases: []) and…
Reads the decisions documents tied to a target phase or task and extracts, per decided TD, only the Recommendation: prose + Libraries: line. Returns a compact ## Decisions Detail for Phase NN / ## Decisions Detail for Task {slug} block ready for direct embedding in context.md. Use when a stage of the plan pipeline…
Reads and filters technical decisions documents tied to a target phase or task. Returns a compact, structured index of all TDs (phase mode: phase-scope doc + ad-hoc docs with the phase in relatedphases; task mode: the task's own ad-hoc doc if present) with their status, scope, topic, decision (if decided), and…
Reads the screen inventory file tied to a target phase or task and returns a compact digest for embedding in context.md's ## UI Inventory section. Emits ### UI ↔ Capability Join (flat table: screen | route | verb | capability | coveringcomponent), ### Server-connected Components, ### Open Questions from Inventory…
Reads prior-phase planning documents and extracts the Conventions to Match bullets AND the Inherited TD Details (verbatim from each prior phase's context.md ## Decisions Detail section) AND the Inherited Deferred Capabilities (verbatim from each prior phase's context.md ## Non-UI / Deferred Capabilities rows with…
Reads docs/project-plan.md and extracts only the target phase's scope (name, capabilities, out-of-scope, deliverables, affected subprojects) plus one-line summaries of the immediate neighbor phases. Returns a compact structured summary so the main thread never loads the full project-plan.
Runs when you submit a prompt, before the agent sees it, running echo 'Identify and activate relevant skills for this task.'. From devfullcycle/mba-ia-greenfield-project.
Front-door for free-text decision needs. Triages user input against existing technical decisions, then routes to one of three branches: Revision (parameter change in existing decided TD), Supersede (Option letter change requires new TD), or Greenfield (no relevant TD exists). Trigger phrases: 'tem decisão sobre X?'…
Apply a Figma → CSS audit report to a Tailwind v4 project. Reads docs/figma-audit.json produced by figma-audit-tokens, validates the CSS file hasn't changed since audit, applies drift fixes and inserts missing tokens following Tailwind v4 conventions (@theme inline for primitives, theme selector blocks for multi-mode…
Audit drift between a Figma variable collection and a project's CSS variables. Captures Figma variables (all modes) plus text/effect styles, parses the project's CSS variables wherever they live (@theme inline, :root, .dark, custom selectors), and emits a structured JSON report at docs/figma-audit.json with drift…
Analyzes a project's tech stack, searches the web for testing best practices, asks the user clarifying questions, and generates a project-specific testing multi-file skill at .claude/skills/testing-guide- / with main SKILL.md and artifact/reference sub-files. Invoke with /generate-test-guide .
Execute a phase implementation plan step by step, respecting dependencies, running the relevant tests after each SI, and only advancing when tests pass. Use whenever the user asks to implement, execute, build, or deliver a planned phase — including variations like 'implement phase X', 'execute phase-02', 'build the…
Execute a phase or task implementation plan step by step, respecting dependencies, running the relevant tests after each SI, and only advancing when tests pass. Use whenever the user asks to implement, execute, build, or deliver a planned phase or task — including variations like 'implement phase X', 'execute…
NestJS architecture patterns and best practices. TRIGGER when: planning or implementing NestJS features (modules, controllers, services, etc), designing modules, implementing auth/security, or writing NestJS tests. DO NOT TRIGGER when: only reading NestJS code without intent to modify, working on frontend, or asking…
Stage 4 of the plan pipeline (phase and task modes). Runs abort-fast preflight checks (mode detection, context.md + validation.md present and fresh, status clean, library-refs.md present if required, resume detection) and writes the final phase-NN-{slug}.md or task-{slug}.md artifact directly from the main thread. The…
Stage 1 of the plan pipeline (phase and task modes). Consolidates project-plan.md (phase mode), decisions docs (phase-scope + ad-hoc tied to the phase, or the task's own + correlated docs), prior phases (or latest completed phase) and testing guide into a lean context.md. Use when the user asks to start planning a…
Generate a technical implementation plan for a project phase. Use whenever the user asks to plan, detail, or generate the technical plan for a phase — including variations like 'plan phase X', 'detail the phase', 'generate phase implementation', 'create the phase-XX.md', or any mention of creating the technical…
Entry point and shared conventions for the plan pipeline (phase and task modes). Invoke directly when the user asks about planning without specifying a stage — this skill orients them to the pipeline stages (context → validate → resolve → build → specs [optional]). For actual work, use the stage skills: plan-context…
Stage 3 of the plan pipeline (phase and task modes). Reads validation.md, asks the user via AskUserQuestion, and applies the answers to the decisions doc (filling Decision: fields, injecting superseded markers, or creating the decisions doc on-the-fly in task-sem-research), context.md (patching the Decisions Index)…
Scaffolds a new custom rule MD file under docs/rules/{plan-validate,plan-build,plan-resolve}/ following the canonical contract documented inline in this SKILL.md. Use when the user asks to create, author, or scaffold a new validation/build/resolve rule, register a new IC prefix, or add a custom check that fires under…
Stage 5 of the plan pipeline (post-build). Generates and syncs /specs/ .plan.md files from phase/task plans, in Microsoft spec-driven format. Specs are later consumed by /implement Step 3a — frontend path loads the playwright-cli Skill for Playwright pattern reference and LLM-authors the E2E test file; backend path…