Project Vision

When to Use

When a project exists (Create complete) and needs its Vision defined.

Inputs

• Project path ({Dept}/Projects/{Project}/)
• User-provided vision/problem statement and requirements

Context Boundary

No other project documents exist at this phase.

Procedure

1. Read the user’s input (vision/problem, requirements, constraints)
2. Copy Forge/Forge_Project/Skills/Project_Create/templates/Vision_Template.md to {Project}_Vision.md in the project folder
3. Update {Project}_Phase.md: set Phase: Vision_Started
4. Fill in the template:
   • Vision or Problem — Set heading to either Vision OR Problem and summarize in one to two paragraphs
   • Background — only if needed
   • Requirements — numbered R1, R2… brief and problem-focused
   • Success Criteria — V1, V2… one per requirement
   • Out of Scope — what this project does not cover
5. Set document status to draft
6. Add sidebar entry by spawning the Page Manager bot via spawnAgent with { botGroup: 'forge', botHandle: 'page-manager' }
7. Build, commit, push
8. Proceed directly to Vision_Eval — do not wait for user approval before evaluation
9. Set document status to review
10. After Vision_Eval converges (no findings, or all findings auto-resolved), present the final Vision to the user for approval
11. Iterate on any remaining user feedback
12. Set document status to approved
13. Update README.md and AGENTS.md to reference the Vision doc
14. Update {Project}_Phase.md: set Phase: Vision_Completed
15. Build, commit, push

Rules

• The user is the primary author; the agent organizes, clarifies, and augments
• Requirements are brief and problem-focused — state what is needed, not how
• Undecided items are permitted — they are resolved during Research
• Each Requirement gets a matching Verification Criterion
• If the project modifies infrastructure (Railway services, databases, volumes, env vars, Docker images), requirements must include verification criteria for data persistence and service version correctness, and the Update_Infrastructure skill must be used during implementation
• Once Plans exist, existing requirements must not be renumbered or removed — retired requirements are annotated [Not required], new ones appended