groundwork

Executor-first workflow with advisor checkpoints at hard decisions AND mandatory gate approval before declaring any task complete. The advisor operates as a strategic technical consultant — providing deep architectural insight, trade-off analysis, and effort-aware recommendations — not just a yes/no gate. ALWAYS required before claiming done.

Implementation orchestration skill. Decompose into vertical slices for maximum coder fan-out, validate behavior. Renamed from bdd-implement — loads implement skill.

Use when creating git commits to ensure consistency with repository patterns and minimal commit messages

Merge time-series PRDs and child PRDs into a single time-neutral document that reads as if the system always worked this way. Use after PRD iterations, before handoff, or when cleaning up docs.

Create the master PRD for a feature with enforced filename conventions, standard content format, and session-level mutation tracking. After creation, MUST ask user for review before proceeding to implementation.

Called by the ORCHESTRATOR only — not by executor agents. Gates plan approval and task completion with APPROVE/REVISE/REJECT verdicts. Use for strategic decisions, architecture trade-offs, and as the mandatory final gate before declaring any task complete.

Primary coding specialist — implements features, fixes bugs, writes and edits code across any number of files. The orchestrator should delegate ALL coding work here.

Final quality gate for plans, code, and architecture decisions. The last line of defense before work is committed. Use for review of significant changes, plan validation, and preventing flawed work from shipping. A false approval costs 10-100x more than a false rejection.

Root-cause analysis, regression isolation, stack trace analysis, build error resolution. Use when something is broken and the cause is unclear. READ-ONLY — recommends fixes, never implements.

UI/UX specialist for intentional, polished experiences. Use for styling, responsive layouts, visual consistency, component architecture, animations, and visual polish. Use when users see it and polish matters. 10x better UI/UX than orchestrator. Best with a model strong at visual taste and high reasoning.

Executor-first workflow with advisor checkpoints at hard decisions AND mandatory gate approval before declaring any task complete. The advisor operates as a strategic technical consultant — providing deep architectural insight, trade-off analysis, and effort-aware recommendations — not just a yes/no gate. ALWAYS required before claiming done.

Mid-session codebase architecture review. All exploration runs in isolated subagents so findings never pollute main context. Surfaces shallow modules, coupling smells, and testability gaps as an HTML report. Use between tasks to retrospect on architecture without bloating the session context window.

Alias for `implement`. Retained for backwards compatibility — load `implement` instead.

Merge time-series PRDs and child PRDs into a single time-neutral document that reads as if the system always worked this way. Use after PRD iterations, before handoff, or when cleaning up docs.

Create the master PRD for a feature with enforced filename conventions, modular content format, and session-level mutation tracking. After creation, MUST ask user for review before proceeding to implementation.

2 hooks across 2 events