plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
What this skill does
# Plan Pipeline Orchestrator
Orchestrates the complete plan-to-execution pipeline. Can run the full pipeline or a single isolated stage.
## Stages
| Stage | Skill | Purpose |
|-------|-------|---------|
| 1 | `/plan-pipeline:ceo-review` | Challenge the brief, lock product direction |
| 2 | `/plan-pipeline:eng-review` | Lock architecture, diagrams, and test matrix |
| 3 | `/plan-pipeline:start` | 5-phase planning: PRD, research, ADRs, task list |
| 4 | `/plan-pipeline:validate` | 2-layer validation before any code is written |
| 5 | `/plan-pipeline:execute` | Worktree isolation, parallel agents, quality gate, PR |
## Usage
```
/plan-pipeline # full pipeline, asks for context
/plan-pipeline --from=start # skip gates, start from planning phase
/plan-pipeline --from=validate # validate an existing plan
/plan-pipeline --from=execute # execute a validated plan
```
## When to Use Each Stage
**ceo-review**: use before any significant feature when the direction is not locked. Especially valuable when the request is specific (specificity signals collapsed solution space).
**eng-review**: use after direction is locked. Required for features with async components, external dependencies, or multi-step flows.
**start**: use for any non-trivial feature touching more than 2 files or involving architecture decisions.
**validate**: always before execute. The cost of validation is negligible against the cost of discovering issues mid-execution.
**execute**: after validate confirms all issues are resolved.
## Workflow
1. **Collect context**: what are we building, and what stage do we start from?
2. **ceo-review**: product direction gate (can be skipped with `--from=eng-review` or later)
3. **eng-review**: architecture gate (can be skipped with `--from=start` or later)
4. **CHECKPOINT**: ask user to confirm direction and architecture before planning
5. **start**: run 5-phase planning, produce `docs/plans/plan-{name}.md`
6. **CHECKPOINT**: present plan for review before validation
7. **validate**: 2-layer validation (structural + specialist agents)
8. **execute**: worktree isolation -> parallel agents -> quality gate -> PR
## Dependency Graph
```
ceo-review
|
eng-review
|
start
|
validate
|
execute
```
## Notes
Each stage writes its output to disk before the next stage begins. If the pipeline is interrupted, resume with `--from=<stage>` using the correct stage name. All decisions are recorded in `docs/plans/plan-{name}.md` and the corresponding ADRs in `docs/adr/`.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.