Skip to content

Extract vision-cycle.md workflow from project.md #136

Description

@snipcodeit

Context

Phase 33 — project.md Decomposition. The vision collaboration cycle (6 stages: vision_intake, domain expansion, structured questioning, vision_synthesis, review, condense) is ~490 lines (~26% of project.md) and only triggers on the Fresh path. It is self-contained with a clear entry point and exit contract. Extracting it makes project.md dramatically shorter and makes the vision cycle independently auditable.

What Already Exists

  • commands/project.md (1979 lines) — contains vision cycle steps starting at approximately line 431: vision_intake, vision_synthesis (with rolling context strategy), spawn_gsd_new_project; cycle is only entered when STATE_CLASS = Fresh
  • Vision agents spawned: vision-researcher (produces .mgw/vision-research.json), vision-synthesizer (produces .mgw/vision-brief.json), vision-condenser (produces .mgw/vision-handoff.md)
  • Rolling summary context strategy documented inline: "agents receive Vision Brief + latest delta, never full transcript"
  • workflows/detect-state.md — created by Extract detect-state.md workflow from project.md #135, required before this extraction (project.md must reference it so vision-cycle.md can assume STATE_CLASS is already set)
  • Schema: templates/vision-brief-schema.json — consumed by vision-synthesizer agent

Description

Extract the 6-stage vision collaboration cycle from commands/project.md into a standalone workflow file at workflows/vision-cycle.md. After extraction, project.md's Fresh routing branch references @workflows/vision-cycle.md.

Technical Approach

  • Extract all vision cycle steps (vision_intake through spawn_gsd_new_project + transition to milestone_mapper) into workflows/vision-cycle.md
  • Document precondition: STATE_CLASS = Fresh (set by detect-state.md)
  • Document postcondition: .mgw/vision-handoff.md exists; GSD new-project has been spawned; ready for milestone_mapper
  • In project.md, replace the ~490 lines with a single @workflows/vision-cycle.md reference under the Fresh branch
  • Preserve the rolling context strategy documentation inside vision-cycle.md

Done When

  • workflows/vision-cycle.md exists with all 6 stages, precondition (STATE_CLASS=Fresh), and postcondition (.mgw/vision-handoff.md created, GSD spawned)
  • commands/project.md references @workflows/vision-cycle.md in the Fresh routing branch instead of containing vision steps inline
  • commands/project.md line count is reduced by ~460 lines (from ~1810 post-Extract detect-state.md workflow from project.md #135 to ~1350)
  • The rolling context strategy (agents receive Vision Brief + latest delta) is documented in vision-cycle.md
  • vision-cycle.md is self-contained and readable without project.md

GSD Route

Quick task or GSD Phase 33 plan.

Phase Context

Phase 33 of 36 — project.md Decomposition. Issues: #135 (blocks this), #136 (this), #137 (blocked on this).

Depends on

#135 — detect-state.md must exist first (project.md routing structure must be clean before extracting the Fresh branch).

Metadata

Metadata

Assignees

Labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions