Menu
Interactive onboarding walkthrough for a new engineer. Use for "give me a tour", "onboard me", "walk me through the codebase".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
Performs an exhaustive 14-dimension bug hunt across the codebase using Draft context (architecture, tech-stack, product) for false-positive elimination. Generates a severity-ranked report with code evidence, data flow traces, and suggested fixes. Optionally writes regression tests. Use when the user asks to find bugs, audit code for defects, scan for vulnerabilities, or says 'hunt bugs', 'find bugs', or 'code audit'.
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.
Structured debugging session. Reproduce, isolate, diagnose, and fix bugs using systematic investigation. Invoked by /draft:new-track for bug tracks or directly for ad-hoc debugging.
Decompose project or track into modules with dependency mapping. Project scope updates architecture.md and derives .ai-context.md. Track scope generates hld.md (always) and lld.md (when --lld or High-complexity module triggers it) — design-mandated artifacts that drive implement, deploy-checklist, and upload sign-off.
Single-module production readiness audit (ACID, resilience, observability). Use to audit one service/module end-to-end — NOT for diff/PR review (use review / quick-review) or bug-finding sweeps (use bughunt).
| name | tour |
| description | Interactive onboarding walkthrough for a new engineer. Use for "give me a tour", "onboard me", "walk me through the codebase". |
Provide an interactive codebase walk-through based on existing architecture and guardrail constraints.
architecture.md into the chat window.draft/architecture.md, draft/tech-stack.md, and draft/guardrails.md.draft/tech-stack.md.architecture.md / guardrails.md.draft/.state/facts.json showing how module constraints have evolved./draft:new-track → spec.md (requirements + classification + approvers) + plan.md (phases/tasks)/draft:decompose → hld.md (always, with graph-derived diagrams) + lld.md (when --lld or High-complexity module)/draft:implement → TDD loop reading lld.md/hld.md for stub generation/draft:upload → blocks git upload for high/mission-critical tracks until HLD §Approvals signed/draft:deploy-checklist → blocks deploy until HLD §Checklist + LLD §Alerting Thresholds populateddraft/tracks/ if any exist; otherwise sketch a hypothetical low-criticality flow./draft:new-track so they understand the artifact loop end-to-end.