phase-transitions

Forge Phase Transitions

This skill defines the 9-phase operational workflow and transition rules.

Phase Overview

Phase	Name	Strict	Completion Criteria
0	Input Normalization	YES	Intent captured, scope identified
1	Semantic Routing	no	Decision axes identified
2	Codebase Reality	no	Reality description complete
3	Mismatch Evaluation	no	Mismatch evaluated (skip if no mismatch)
4	Structured Questioning	YES	All questions answered
5	Option Synthesis	no	Options presented
6	Workflow Creation	no	Workflow defined or skipped
7	Execution	YES	User confirmation received, execution complete
8	Validation	no	All validations passed

Strict Phases (0, 4, 7)

These phases block non-allowed tools:

Phase 0 - Input Normalization

• Allowed: Read, Glob, Grep, AskUserQuestion
• Blocked: Write, Edit, Bash (no execution before intent is clear)
• Must complete: Intent statement AND scope identification

Phase 4 - Structured Questioning

• Allowed: AskUserQuestion, Read
• Blocked: Write, Edit, Task (no execution during questioning)
• Must follow: Structured Dialogue Contract format
• Must complete: All questions answered

Phase 7 - Execution

• Allowed: All tools (after user confirmation)
• Requires: Explicit user confirmation before any execution
• Blocked: Nothing (but only after confirmation)

Non-Strict Phases (1, 2, 3, 5, 6, 8)

These phases warn but do not block:

• Warning logged to stderr
• Execution proceeds

Phase Transition State Machine

[0: Input Normalization] ──(intent captured)──> [1: Semantic Routing]
         │
         │ (STRICT: must complete before proceeding)
         │
[1: Semantic Routing] ──(axes identified)──> [2: Codebase Reality]
         │
[2: Codebase Reality] ──(description complete)──> [3: Mismatch Evaluation]
         │
[3: Mismatch Evaluation] ─┬─(mismatch found)──> [4: Structured Questioning]
                          │
                          └─(no mismatch)──> [5: Option Synthesis]
         │
[4: Structured Questioning] ──(answers received)──> [5: Option Synthesis]
         │
         │ (STRICT: must follow Dialogue Contract)
         │
[5: Option Synthesis] ──(options presented)──> [6: Workflow Creation]
         │
[6: Workflow Creation] ─┬─(workflow defined)──> [7: Execution]
                        │
                        └─(no workflow)──> [7: Execution]
         │
[7: Execution] ──(user confirmation)──> [execution proceeds]
         │
         │ (STRICT: requires user confirmation)
         │
[7: Execution] ──(execution complete)──> [8: Validation]
         │
[8: Validation] ──(all passed)──> [COMPLETE]

Workflow Versioning

When a workflow is confirmed in Phase 7:

• workflow_version is set to 1
• Strict enforcement activates for the workflow

If the workflow is modified:

• workflow_version increments
• workflow_confirmed resets to false
• User must reconfirm before strict enforcement resumes

Latent vs Promoted Phases

• Latent: Non-strict phases exist only in reasoning
• Promoted: Any phase can be promoted to strict when:
  • Skipping would cause semantic failure
  • Order affects correctness
  • User requests strict enforcement

Related

• config/phase-definitions.yaml for machine-readable definitions
• scripts/forge-daemon.py for state management
• scripts/pretool-hook.py for enforcement