Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navapbc/digital-service-orchestra/plugin install dsoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/navapbc/digital-service-orchestra/preplanning)<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/preplanning"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/preplanning/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/preplanning"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/preplanning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00150 | $0.20105 |
| Opus 5 | $0.00075 | $0.10053 |
| Sonnet 5 | $0.00030 | $0.04021 |
| Haiku 4.5 | $0.00015 | $0.02011 |
Grade A, and why
preplanning scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 1,342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup Configuration
At the very start of execution (immediately after passing the SUB-AGENT-GUARD check), read the interactive mode flag:
PLUGIN_SCRIPTS="${CLAUDE_PLUGIN_ROOT}/scripts"
PREPLANNING_INTERACTIVE=$(bash "$PLUGIN_SCRIPTS/read-config.sh" preplanning.interactive 2>/dev/null || echo 'true') # shim-exempt: internal orchestration script
PREPLANNING_INTERACTIVE=$(echo "$PREPLANNING_INTERACTIVE" | tr '[:upper:]' '[:lower:]')
# Default: true (interactive) when the key is absent or empty
if [[ -z "$PREPLANNING_INTERACTIVE" ]]; then
PREPLANNING_INTERACTIVE="true"
fi
Default is true (interactive) when the key is absent — new projects without the key should default to interactive mode. Only set preplanning.interactive=false in .claude/dso-config.conf for automated pipelines.
Pre-Planning: High-Fidelity Story Mapping
Act as a Senior Technical Product Manager (Google-style) to audit, reconcile, and decompose a ticket Epic into prioritized User Stories with measurable Done Definitions that bridge the epic's vision to task-level acceptance criteria.
Supports dryrun mode. Use /dso:dryrun /dso:preplanning to preview without changes.
Usage
/dso:preplanning # Interactive epic selection
/dso:preplanning <epic-id> # Pre-plan specific epic
/dso:preplanning <epic-id> --lightweight # Enrich epic without creating stories (used by /dso:sprint for MODERATE epics)
Arguments
<epic-id>(optional): The ticket epic to decompose. If omitted, presents an interactive list of open epics.--lightweight(optional): Enrich the epic with done definitions and considerations without creating child stories. ReturnsENRICHEDorESCALATED. Used by/dso:sprintfor MODERATE-complexity epics. If the scope scan discovers COMPLEX qualitative overrides, returnsESCALATEDso the orchestrator can re-invoke in full mode.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- docs/example-reconciliation.md 2.0 KB
- docs/review-criteria.md 5.4 KB
- docs/reviewers/accessibility.md 3.0 KB
- docs/reviewers/maintainability.md 4.9 KB
- docs/reviewers/performance.md 4.1 KB
- docs/reviewers/reliability.md 4.0 KB
- docs/reviewers/security.md 3.5 KB
- docs/reviewers/testing.md 5.5 KB
- prompts/lightweight-mode.md 3.4 KB
- prompts/phase-e-adversarial-review.md 15 KB
- prompts/research-process.md 4.3 KB
- prompts/ui-designer-dispatch-protocol.md 18 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 1,342 lines · 150 tokens per session scan A a1826fa83878
preplanning is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 150 tokens to every session and 20,105 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.