Plan the Iteration
RIN-3 Order: #3 Construction Has Dependencies
Updated 1 month, 2 weeks ago
Guidance
Objective
Invoke Plan the Iteration (PIN) for the approved goal and produce an accepted, executable delivery manifest.
Procedure
- Pass PIN the Iteration Frame, Charter, relevant architecture/process context, open gating tickets, and accepted IIPs.
- Follow PIN's own activity order and planning rules. Enter enforced ADE planning mode when available.
- Fan out bounded investigation only where PIN permits and only when workers have distinct outputs or read-only scopes.
- Converge estimates, dependencies, codebase footprints, checkpoints, parallel groups, and human gates into one manifest/milestone.
- Obtain the PIN approval required before execution.
Failure handling
Do not invoke MIN with a speculative, internally inconsistent, or unapproved plan. If planning reveals that the goal does not fit, return to Set the Iteration Goal and narrow it.
Completion evidence
The accepted PIN output names every scenario/work item, dependency, codebase footprint, checkpoint command, time budget, parallel group, and approval gate. Its goal and iteration ID match the Iteration Frame.
Details
- Order:
- #3
- Phase:
- Predecessor:
- RIN-2 Set the Iteration Goal
- Successor:
- RIN-4 Execute the Iteration
- Created:
- Sep 21, 2026
- Last Updated:
- Sep 21, 2026
Workflow
Run the Iteration
Thin orchestration shell around PIN and MIN. Each cycle determines cadence and iteration length, selects one evidence-backed goal, invokes PIN, …
View WorkflowAssigned Agent
Delivery Manager (DM)
Single merged PM/DM role. Staffed at Kickoff. Owns the Charter, is the recipient of all …
Required Skills
No skills linked
Rules
No rules linked.
Input Artifacts 2
-
Iteration Frame
Document
Required
Produced by: Determine Cadence & Iteration Length -
Iteration Goal Contract
Document
Required
Produced by: Set the Iteration Goal
Output Artifacts
No output artifacts