with one click
orchestrateplan
// Brainstorm and create phased enhancement plan for a target repo - PR sizing, phase selection, task breakdown
// Brainstorm and create phased enhancement plan for a target repo - PR sizing, phase selection, task breakdown
Use this skill when you need to create clear, concise summaries of information. This includes summarizing long documents, articles, meeting notes, technical documentation, research papers, or any text that needs to be condensed while preserving key information. The skill provides techniques for extractive and abstractive summarization, bullet-point formatting, and executive summaries.
Add comprehensive CI workflows to a target repo - lint, test, build, security scanning, dependabot, scorecard, action pinning
Add pre-commit hooks, linting, CLAUDE.md, and foundational .claude/ setup to a target repo
Review all orchestration PRs before merge - per-PR checks, cross-PR consistency, and coordinated approval
Scan and assess a target repository - tech stack, CI maturity, security posture, test coverage, supply chain health
Add security governance to a target repo - CODEOWNERS, SECURITY.md, CONTRIBUTING.md, LICENSE, .gitignore audit
| name | orchestrate:plan |
| description | Brainstorm and create phased enhancement plan for a target repo - PR sizing, phase selection, task breakdown |
flowchart TD
START(["/orchestrate:plan"]) --> READ["Read scan report"]:::orch
READ --> PRESENT["Present findings"]:::orch
PRESENT --> BRAINSTORM["Brainstorm with developer"]:::orch
BRAINSTORM --> SELECT["Select applicable phases"]:::orch
SELECT --> SIZE["Size PRs (600-700 lines)"]:::orch
SIZE --> WRITE["Write plan document"]:::orch
WRITE --> DONE([Plan complete])
classDef orch fill:#FF9800,stroke:#333,color:white
Follow this diagram as the workflow.
Take the scan report and turn it into a concrete phased enhancement plan. This is Phase 1 — interactive brainstorming with the developer, no PRs.
orchestrate:scan has produced a scan reportScan report must exist:
cat /tmp/kagenti/orchestrate/<target>/scan-report.md
Review the Gap Summary and Recommended Phases sections.
Summarize the key gaps in plain language. Use AskUserQuestion to confirm understanding and gather context about the repo's priorities.
Not all repos need all phases. Use AskUserQuestion to decide:
| Gap Found | Phase | Default |
|---|---|---|
| No pre-commit config | orchestrate:precommit | Always (foundation) |
| No/incomplete CI workflows or security scanning | orchestrate:ci | Yes if missing |
| No/few tests (<5 test files) | orchestrate:tests | Yes if low coverage |
| No CODEOWNERS/SECURITY.md/LICENSE | orchestrate:security | Recommended |
No .claude/skills/ directory | orchestrate:replicate | Always (last phase) |
Default order: precommit → tests → ci → security → replicate
Tests come before CI (so CI can run them) and before security (so code refactoring for security fixes has test coverage as a safety net). Pre-commit is always first (it validates subsequent PRs). Replicate is always last.
Target 600-700 lines per PR. For each phase:
Save to /tmp/kagenti/orchestrate/<target>/plan.md:
# Enhancement Plan: <target>
**Generated from scan:** YYYY-MM-DD
**Tech stack:** <language>
**Phases:** <count>
## Phase 2: Pre-commit (PR #1, ~NNN lines)
- [ ] Add .pre-commit-config.yaml
- [ ] Add linting config
- [ ] Create CLAUDE.md
- [ ] Create .claude/settings.json
## Phase 3: Tests (PR #2, ~NNN lines)
- [ ] Set up test framework
- [ ] Add test configuration
- [ ] Write initial tests for critical paths
## Phase 4: CI (PR #3, ~NNN lines)
- [ ] Add lint/test/build workflow (ci.yml)
- [ ] Add security scanning workflow (security-scans.yml)
- [ ] Add dependabot.yml (all detected ecosystems)
- [ ] Add scorecard workflow
- [ ] Add action pinning verification
- [ ] Add container build workflow (if Dockerfiles exist)
## Phase 5: Security Governance (PR #4, ~NNN lines)
- [ ] Create CODEOWNERS
- [ ] Create SECURITY.md
- [ ] Create CONTRIBUTING.md
- [ ] Verify/add LICENSE
- [ ] Audit .gitignore
## Phase 6: Replicate (PR #5)
- [ ] Copy orchestrate:* skills to target
- [ ] Adapt references
- [ ] Update CLAUDE.md
- [ ] Validate skills
Initialize phase tracking:
cat > /tmp/kagenti/orchestrate/<target>/phase-status.md << 'EOF'
# Phase Status: <target>
| Phase | Status | PR | Date |
|-------|--------|----|------|
| scan | complete | — | YYYY-MM-DD |
| plan | complete | — | YYYY-MM-DD |
| precommit | pending | | |
| tests | pending | | |
| ci | pending | | |
| security | pending | | |
| replicate | pending | | |
EOF
Then invoke the first applicable phase skill (usually orchestrate:precommit).
orchestrate — Parent routerorchestrate:scan — Prerequisite: produces the scan reportorchestrate:precommit — Usually the first PR-producing phase