Agent skills for VS Code

Use when deciding which layer a piece of code belongs in (domain, application, or infrastructure), when business rules are mixed with…

Rewrites complex concepts into jargon-free, plain language while automatically generating structured Org-mode notes.

Produce an implementation-ready plan for a software change by inspecting the actual repository, tracing affected execution paths…

Turns an established product or design direction into one finite delivery outcome and autonomous-ready work.

Use before any implementation — understands the request, discovers project context, and proposes a concise plan for user approval before…

Interactive briefing of a plan file — explains reasoning, schema decisions, component choices.

Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes…

Recommend before substantial implementation work, but invoke only after the user agrees.

Design feature architecture using the architect agent

Use when reviewing a plan before implementation begins.

Use when presenting an implementation plan, a migration, a refactor, a roadmap, or any multi-step change to someone who decides whether it…

Break a milestone goal into epics and tasks with dependency ordering, acceptance tests, and task manager ticket creation.

Use when starting a complex multi-step task to create an approved plan, track todos in SQL, and execute with checkpoints

Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate…

THE BRAIN behind /toh-plan — analyzes the request or PRD, writes .toh/plan.md per the orchestration-protocol Section D schema (plans are…

Creates a product requirement doc (PRD) and an implementation plan (IMPL), suitable for a prototype

Review development plans for issues, missing considerations, architectural violations, and alternatives.

Carmack-level plan review via rp-cli context builder + chat.

Get Gemini's review of Claude's implementation plans.

Start from a detailed product description, and systematically turn that into an implementation specifications.

Convert a PLAN into GitHub issues with native sub-issue hierarchy.