popoffvg/plan-router
skills/plan-router/SKILL.md
Use when creating or refining any implementation plan, roadmap, or task breakdown. Routes to the appropriate C4 phase skill based on current plan state.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles plan-routerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 4:44 AM105.2s1 file scanned
SKILL.md
- name:
- plan-router
- description:
- Use when creating or refining any implementation plan, roadmap, or task breakdown. Routes to the appropriate C4 phase skill based on current plan state.
plan-router — Plan Router
Routes planning work to the correct C4 phase skill. Be declarative, constraint-first, and concrete (real file paths, real types).
Routing logic
- Read
_notes/plan.md(or note its absence). - Determine the current phase by checking which C4 levels have fixed decisions:
| Condition | Route to | |---|---| | No plan or no Description | plan-context (L1) | | L1 decisions fixed, L2 missing/open | plan-container (L2) | | L1+L2 fixed, L3 missing/open | plan-component (L3) | | L1+L2+L3 fixed, L4 missing/open | plan-code (L4) | | All levels fixed | plan-verify |
- Skip levels when scope is contained within a single level (e.g., a bugfix may start directly at L4). State the skip explicitly:
Skipping L1–L3: scope is a single-function change. - If routing confidence is low (missing plan context, conflicting decisions, unclear scope), do not guess. Ask up to 3 targeted clarification questions, then route.
Quick go-ahead handling (reduce friction)
If you already proposed a routing decision or next planning action and the user replies with a short confirmation (for example: "let's do", "do it", "go ahead", "ok"), treat that as approval to execute the last concrete proposal immediately.
- Do not ask the user to restate which option unless there are multiple unresolved options.
- Do not repeat the routing explanation unless the user asks for rationale again.
- If multiple options remain, ask exactly one disambiguation question.
Output contract (router response)
Always return a compact routing decision in this shape:
Routing Decision
- selected phase skill: <plan-context|plan-container|plan-component|plan-code|plan-verify>
- why: <1-2 concrete reasons tied to plan state>
- evidence: <file/section names used>
- skipped levels: <none|L1-L2... + explicit reason>
- next action: <run selected phase skill>
If _notes/plan.md is absent, return plan-context and explicitly say "starting from L1 because plan file is missing".
Phase skills
- plan-context — L1: system boundaries, actors, scope decisions, seed glossary
- plan-container — L2: services, databases, protocols, technology choices
- plan-component — L3: modules, interfaces, dependency directions
- plan-code — L4: algorithms as TS pseudocode (see
work-plan-flow), data structures, patterns
Plan contract
Constraints, layout, and traceability rules live in work-plan (router) and work-plan-flow (TS pseudocode patterns). No separate contract skill.
Autoresearch rules
Can change: templates, command names, constraint wording, mapping format Cannot change: checkbox contract, criteria<>TODO traceability, declarative-first planning, phase routing order Min sessions before eval: 5 Runs per experiment: 3
Related Skills
popoffvg/test-set-write
testing
VerifiedTrustedCommunity
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-set-verify
testing
VerifiedTrustedCommunity
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-harness-plugin
tools
VerifiedTrustedCommunity
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-bdd
development
VerifiedTrustedCommunity
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.
2SKILL.mdUpdated Jun 2, 2026