| name | plan |
| description | Create an execution-ready Parallax plan grounded in repository evidence and explicit verification. |
| argument-hint | [goal] |
| user-invocable | true |
Plan
Pass the current Claude session ID to parallax_plan, then plan $ARGUMENTS without modifying files.
- Read project instructions, manifests, architecture, tests, and the nearest comparable implementation.
- Resolve material ambiguity. State the four invariants with concrete owners and paths.
- Analyze nominal behavior, boundaries, errors, security, concurrency, compatibility, rollback, and observability.
- For cross-subsystem or high-risk work, run the Hyperplan skill and incorporate only critiques supported by evidence.
- Produce ordered, atomic items. Each item must name its files or component, observable acceptance criterion, and targeted check.
- Identify assumptions, external blockers, and deferred work explicitly.
A good plan is short enough to execute, detailed enough for another agent to verify, and does not claim certainty unsupported by repository evidence.