Project intake methodology for gathering specifications, validating requirements, and generating runbooks. Use when starting new projects, gathering requirements, or validating project scope.
From opspal-corenpx claudepluginhub revpalsfdc/opspal-commercial --plugin opspal-coreThis skill is limited to using the following tools:
methodology.mdpatterns.mdtroubleshooting.mdReorganizes X and LinkedIn networks: review-first pruning of low-value follows, priority-based add/follow recommendations, and drafts warm outreach in user's voice.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
| Phase | Purpose | Output |
|---|---|---|
| 1 | Form Generation | intake-form.html |
| 2 | Data Collection | intake-data.json |
| 3 | Validation | Validation result with errors/warnings |
| 4 | Context Gathering | Context from SF/Asana/runbooks |
| 5 | Runbook Generation | PROJECT_RUNBOOK.md |
| 6 | Asana Creation | Project with requirement tasks |
| Section | Weight | Required |
|---|---|---|
| Project Identity | 15% | Yes |
| Goals & Objectives | 20% | Yes |
| Scope | 20% | Yes |
| Data Sources | 10% | No |
| Timeline & Budget | 15% | Yes |
| Dependencies & Risks | 10% | No |
| Technical Requirements | 5% | No |
| Approval & Sign-off | 5% | No |
Ready for handoff: Score >= 80% AND no validation errors
/intake # Interactive workflow
/intake --form-data ./data.json # Process existing data
/intake --validate ./data.json # Validate only
/intake-generate-form # Generate form only
Uses depth-first search (DFS) to detect cycles:
A depends on B → B depends on C → C depends on A = CIRCULAR
See supporting files:
methodology.md - Complete 6-phase workflow guidepatterns.md - Common intake patterns and templatestroubleshooting.md - Common issues and solutions