メニュー
Generates a right-sized, stack-aware testing strategy specifying what to unit test, integration test, E2E test, and manually test -- avoiding both under-testing and 100%-coverage dogma.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Master orchestrator for the Solo Dev Suite — a collection of lifecycle skills (scope guardian, sprint planner, pricing architect, launch readiness, ADR generator, security audit, integration mapper, auto-docs, tech debt register, testing strategy) that share a central Project Profile. Triggers on requests like "solo dev suite", "run the suite on {project}", "set up a project profile", "what suite skills apply here", "show my projects", or any direct invocation of a child skill by name when no profile exists yet. Not for one-off tasks with no ongoing project — those stay as standalone skills.
Generates and maintains Architecture Decision Records (ADRs) in the Michael Nygard format -- numbered, sequentially stored Markdown docs capturing context, options considered, decision, and consequences. Triggers on "generate an ADR", "record this decision", "log architecture decision", "why did I choose X", "add an ADR", or "list my ADRs". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Not for runtime config changes (those are just code) or meeting notes (use a wiki).
Generates and maintains project documentation (README, SETUP, ARCHITECTURE, CHANGELOG) by pulling from the profile and sibling sidecars. Re-runnable at every milestone so docs stay current without being a full-time job.
Scans a codebase for local-to-cloud migration blockers -- hardcoded paths, LAN URLs, dev-only bypasses, missing deploy configs -- and produces a scored readiness report. Triggers on "deploy readiness", "ready to deploy", "can I host this", "cloud migration check", "scan for local stuff", "deployment blockers". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Unlike security-audit (a checklist), this skill actually reads code.
Generates a customized design-exploration loop prompt for an existing project by discovering its stack, domain, and aesthetic, then tailoring references and constraints accordingly. Triggers on requests like "design loop on {project}", "refine the UI of this project", "explore design directions for {project}", "make this look more polished", "visual refresh", "modernize the UI", or "UI audit". Not for greenfield design, CSS debugging, or single-component tweaks — requires a target directory with an existing UI surface to analyze.
Comprehensive feature-enhancement discovery skill. Points at any codebase — the current Claude Code workspace, a local source folder, or a Forgejo/Git repo URL — scans the full stack, inventories existing features, surfaces incomplete/stub work, then researches comparable apps and platforms to generate a prioritized list of value-add enhancements. Outputs a structured FEATURE_ENHANCEMENTS.md report. Trigger whenever the user says: "feature enhancement", "what features are we missing", "analyze my codebase for improvements", "compare to competitors", "what should I add next", "audit my app", "run the enhancement skill", "scan for TODOs and features", "what else should this do", or points at a project and asks for improvement ideas. Also triggers when user wants to know how their app stacks up against similar tools or what features competitors have that they don't.
| name | testing-strategy |
| version | 1.0.0 |
| description | Generates a right-sized, stack-aware testing strategy specifying what to unit test, integration test, E2E test, and manually test -- avoiding both under-testing and 100%-coverage dogma. |
"High" means the high-risk modules are well covered. Not a number. Goodhart's law applies.
A strategy that says "don't bother testing UI components" is useful. Silence on UI components is ambiguous.
The review_cadence field (monthly/quarterly/biannual/annual) drives staleness warnings on show.
Create the initial testing strategy.
echo '{ full payload }' | python scripts/testing_tool.py design <slug> --from-stdin
Display strategy with staleness check.
python scripts/testing_tool.py show <slug>
python scripts/testing_tool.py show <slug> --category unit
python scripts/testing_tool.py show <slug> --json
Update the strategy (requires reason).
echo '{"reason":"Adding Stripe, need integration tests","categories":{"integration":{...}}}' \
| python scripts/testing_tool.py iterate <slug> --from-stdin
Mark strategy as reviewed, resets staleness timer.
python scripts/testing_tool.py review <slug>
Generate TESTING_STRATEGY.md.
python scripts/testing_tool.py render <slug>
Remove sidecar.
python scripts/testing_tool.py delete <slug> --yes
| File | Purpose |
|---|---|
scripts/testing_tool.py | CLI with all subcommands |
templates/testing.schema.json | Sidecar JSON Schema |
templates/TESTING_STRATEGY.md.tmpl | Rendered doc template |