planner
Skill1 starsChanged 3 months agoMITView on GitHub
This replaces "did we run everything?" with "here is a measurable plan covering X% of relevant surfaces." This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining. Prerequisite: The planner requires a domain profile. If the target has no prior recon, run the recon skill first, then the domain-model skill to generate a domain profile, then use the planner.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- GravionLabs/skillstheir own version, first seen Nov 15, 2026
- VinayKhandia/no-sloptheir own version, first seen Nov 15, 2026
- scottconverse/productteamtheir own version, first seen Nov 15, 2026
- Tariux/AI-Skills-Not-Awesometheir own version, first seen Nov 15, 2026
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 12, 2026
- AJschoons/robowrighttheir own version, first seen Nov 8, 2026
Used with
Projects with it also use executor, reviewer and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MooseDesign1Skillexecutor
Main executor agent. Triggered by /executor, or natural language such as: "build this feature", "execute the feature", "start building", "map the codebase", "scan the code", "resume building", "continue the build", "dev status", "where are we on development", "what's built". Do NOT trigger for /planner, /plan:project, /plan:feature, /plan:status, /product-designer, /pd:*, /ds-designer, /ds-*.
Also in 3 projects that use this
MicrosoftSkillreviewer
ASP.NET Core ハンドブックの記事をレビューする。Use when: 記事をレビューする、ドキュメントを校正する、コードレビューする、PRをレビューする。技術ドキュメントのレビュー、品質チェック、校正。
Also in 5 projects that use this
JohnJBorenSkilldebugger
Systematic debugging workflows, root cause analysis, and troubleshooting patterns
Also in 3 projects that use this
JetBrainsSkillreview-plan
Manually re-run the autonomous plan review (Phase 2 — consistency + structural). The same review runs automatically as the first phase of /execute-tracks; this command is for re-runs after inline replanning or whenever the plan needs explicit re-validation. TRIGGER when: user asks to re-validate the plan after inline replanning; user requests explicit plan review outside /execute-tracks. SKIP: /execute-tracks already running State 0 in this session (autonomous Phase 2 path will fire) — do not double-run.
Also in 3 projects that use this
tesla0225Skillorchestrator
Issue/要件を受けたら分解→担当割当→実装→検証→統合を回す手順。未整備なら /repo-init でbootstrap。
Also in 4 projects that use this
Harut8Skillarchitect
Also in 3 projects that use this
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- penpot/penpot★ 62ksame name
- am-will/codex-skills★ 1ksame name
- toonight/get-shit-done-for-antigravity★ 952same name
- Vinix24/vnx-orchestration★ 63same name
- openclosed-org/axum-harness★ 48same name
- Tariux/AI-Skills-Not-Awesome★ 48same name
- FlineDev/TandemKit★ 42same name
- digitalocean-labs/do-app-platform-skills★ 38same name
- MooseDesign1/DDD-DesignDrivenDevelopment★ 9same name
- jackstine/forgectl★ 8same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 31 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
Start with generate-plan for the full plan.
- Very specific: line 41
Use generate-plan-safe if you only want safe, non-destructive items.
- Very specific: line 42
Follow with visualize-plan and validate-plan to review before execution.
- Very specific: line 43
After execution, use the plan-vs-results runbook to feed findings back into the coverage matrix.
“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Planner
Overview
Domain-driven ranked test plan generator. Consumes the Domain Model (archetypes + surfaces), the Asset Graph (recon data), the Technique KB catalog, and the Coverage Ledger. Outputs a prioritized list of workflows to execute — ranked by business impact, surface prevalence, vulnerability severity, signal quality, coverage gaps, and tool availability.
This replaces "did we run everything?" with "here is a measurable plan covering X% of relevant surfaces."
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
Quick Reference
- Skill:
planner - Severity range:
info - Required tools:
python3,jq,yq - Expected input files: Domain profile JSON (from
domain-model/), Technique YAML catalog (fromtechnique-kb/), optional coverage matrix YAML or JSON - Scope check: The planner itself does not execute intrusive tests — it plans them. Ensure scope authorization exists before executing any plan items.
- Secret handling: Any auth headers, session tokens, cookies, or bearer credentials referenced in domain profiles or plan items are local-only and must be redacted before sharing; sanitize plan artifacts and never commit secrets (covered by gitignore).
When to Use
Trigger phrases:
- "create a test plan", "generate a plan", "ranked plan", "what should I test", "prioritize my testing", "plan my engagement", "coverage-based plan"
- "plan", "planning", "test strategy", "engagement plan", "plan vs results"
Prerequisite: The planner requires a domain profile. If the target has no prior recon, run the recon skill first, then the domain-model skill to generate a domain profile, then use the planner.
Decision Tree
User provides target + wants a plan
│
├── Domain profile exists? ── No ──> Run recon → domain-model → retry
│
├── Technique catalog populated? ── No ──> Warn user, plan will be empty
│
├── Coverage matrix available? ── No ──> Plan treats all techniques as gaps
│
└── Generate plan ──> Review ──> Execute ──> Plan vs ResultsWorkflow Selection
- Start with
generate-planfor the full plan. - Use
generate-plan-safeif you only want safe, non-destructive items. - Follow with
visualize-planandvalidate-planto review before execution. - After execution, use the
plan-vs-resultsrunbook to feed findings back into the coverage matrix.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs |
generate-plan | Generate full ranked test plan from domain profile + techniques + coverage | .claude/skills/planner/scripts/generate_plan.py | Plan JSON file |
generate-plan-safe | Generate plan excluding intrusive and destructive techniques | .claude/skills/planner/scripts/generate_plan.py | Plan JSON file |
visualize-plan | Convert plan JSON to readable markdown or HTML | .claude/skills/planner/scripts/plan_visualizer.py | Markdown or HTML file |
validate-plan | Validate plan JSON against plan_schema.yaml for structural correctness | .claude/skills/planner/scripts/plan_validator.py | Validation report (stdout) |
import-workflow | Import portable open-kritt-workflow v2 JSON into a playbook YAML | tools/import_workflow.py | Playbook YAML file |
apply-model-overrides | Apply per-depth model overrides to a plan (Kritt-style) | .claude/skills/planner/scripts/model_overrides.py | Plan with model_override per item |
Runbooks
| Runbook | Purpose | Path |
| Generate Plan | Step-by-step plan generation | .claude/skills/planner/runbooks/generate-plan.md |
| Review Plan | Review plan for safety, scope, completeness | .claude/skills/planner/runbooks/review-plan.md |
| Execute Plan | Execute plan items, collect evidence, record results | .claude/skills/planner/runbooks/execute-plan.md |
| Plan vs Results | Compare plan to actual results, update coverage matrix | .claude/skills/planner/runbooks/plan-vs-results.md |
Scoring Model
Each technique is scored on 6 dimensions and weighted to produce a final score [0,1]:
| Dimension | Weight | What it measures |
| Business Impact | 0.30 | Archetype severity weight × technique severity mapping |
| Surface Prevalence | 0.20 | Match between technique surfaces and target's detected surfaces |
| Vulnerability Severity | 0.20 | Direct mapping from technique severity field |
| Detection Signal Quality | 0.15 | Number and specificity of positive/negative expected signals |
| Coverage Gap Urgency | 0.10 | Whether the technique fills a prior gap (1.0 = not covered, 0.0 = covered) |
| Tool Availability | 0.05 | Fraction of required tools found in PATH |
Priority tiers: critical (≥0.80), high (≥0.60), medium (≥0.35), low (<0.35)
Technique YAML Format (expected in technique-kb/techniques/)
id: "xss-reflected-get"
name: "Human-readable technique name"
category: "xss"
severity: "critical|high|medium|low|info"
description: "What this technique detects"
standards:
wstg: ["WSTG-INPV-01"]
asvs: []
api_top10: []
vrt: []
cwe: ["CWE-79"]
applies_to:
archetypes: ["all"]
surfaces: ["all-parameterized-endpoints"]
requires:
auth: "none"
inputs: ["parameterized URLs"]
tools: ["curl", "dalfox"]
signals:
positive:
- "Payload echoed in response without sanitization"
negative:
- "Content-Type prevents script execution"
safety:
intrusive: false
data_modifying: false
rate_limited: false
requires_approval: false
evidence:
required:
- "raw_request"
- "raw_response"
- "screenshot"
workflow_mapping:
skill: "xss"
workflow: "reflected-param-test"Evidence Required
The planner itself does not produce evidence — it produces a plan. Each plan item specifies what evidence to collect during execution:
raw_request— full HTTP request with headersraw_response— full HTTP response with headers and bodyscreenshot— visual evidence of the findingpoc_script— reproducible proof of concepttool_output— raw tool output logstimestamp— ISO 8601 execution time
Output Files
| File | Contents |
plan.json | Full ranked plan in plan_schema format |
plan.md / plan.html | Human-readable visualizations |
coverage.json | Updated coverage matrix (after plan-vs-results) |
References
- Source of truth:
skill.yaml - Scoring rules:
ranking_rules.yaml - Plan schema:
plan_schema.yaml - Runbooks:
runbooks/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

