[Issue #41] Update /vision command for product-level only #48

HugoNijhuis · 2026-01-07T19:24:42Z

HugoNijhuis commented

2026-01-07 19:24:42 +00:00

Closes #41

Summary

Updates /vision command to be explicitly product-level, distinct from /manifesto which handles organization-level vision.

Changes

Architecture table: Shows clear hierarchy (Organization → Product → Goals)
Manifesto reference: Process now checks for manifesto first for org context
Output format: Includes "Organization Context" section linking to manifesto
Guidelines: Clarify when to use /manifesto vs /vision
Inheritance model: Product personas/jobs extend (not duplicate) org-level ones

Relationship

Command	Level	Document
`/manifesto`	Organization	`manifesto.md`
`/vision`	Product	`vision.md`
`/vision goals`	Goals	Gitea milestones

Test Plan

/vision command updated for product-level scope
References organization manifesto
Clear distinction from /manifesto command
Works in product repos (guidance to use /manifesto in architecture repo)

🤖 Generated with Claude Code

Closes #41 ## Summary Updates `/vision` command to be explicitly product-level, distinct from `/manifesto` which handles organization-level vision. ## Changes - **Architecture table**: Shows clear hierarchy (Organization → Product → Goals) - **Manifesto reference**: Process now checks for manifesto first for org context - **Output format**: Includes "Organization Context" section linking to manifesto - **Guidelines**: Clarify when to use `/manifesto` vs `/vision` - **Inheritance model**: Product personas/jobs extend (not duplicate) org-level ones ## Relationship | Command | Level | Document | |---------|-------|----------| | `/manifesto` | Organization | `manifesto.md` | | `/vision` | Product | `vision.md` | | `/vision goals` | Goals | Gitea milestones | ## Test Plan - [x] /vision command updated for product-level scope - [x] References organization manifesto - [x] Clear distinction from /manifesto command - [x] Works in product repos (guidance to use /manifesto in architecture repo) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

HugoNijhuis added 1 commit 2026-01-07 19:24:42 +00:00

Update /vision command for product-level only c0ef16035c

Clarifies /vision is for product-level vision, distinct from /manifesto
which handles organization-level vision.

Changes:
- Added architecture table showing org vs product vs goals levels
- Process now checks for manifesto first for org context
- Output format includes Organization Context section
- Guidelines clarify when to use /manifesto vs /vision
- Product personas/jobs extend (not duplicate) org-level ones

Closes #41

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

HugoNijhuis commented

2026-01-07 19:25:23 +00:00

AI Code Review

This is an automated review generated by the code-reviewer agent.

Summary

This PR successfully establishes a clear hierarchy between organization-level manifesto and product-level vision. The architecture table is particularly effective at communicating the three-layer model.

Findings

Code Quality

Structure: Well organized with logical progression from context to process to output format
Architecture table: The expanded table (org/product/goals + commands) makes the relationship crystal clear
Process flow: Steps 1-5 properly sequence manifesto check → vision check → creation or display

Potential Bugs

No functional issues found. The command maintains backward compatibility while adding new context.

Documentation Completeness

Output format: Includes "Organization Context" section with manifesto reference
Milestone descriptions: Now show structured format (For:/Job:/Success:) which traces back to vision
Guidelines section: Properly distinguishes when to use /manifesto vs /vision
Architecture repo note: Smart addition - "If this is the architecture repo itself, use /manifesto instead"

Style Notes

Consistent with existing command documentation format
Markdown formatting is clean and readable

Verdict

LGTM

The hierarchy is clear, the distinction between /manifesto and /vision is well-articulated, and the output format properly references organization context. Ready to merge.

## AI Code Review > This is an automated review generated by the code-reviewer agent. ### Summary This PR successfully establishes a clear hierarchy between organization-level manifesto and product-level vision. The architecture table is particularly effective at communicating the three-layer model. ### Findings #### Code Quality - **Structure**: Well organized with logical progression from context to process to output format - **Architecture table**: The expanded table (org/product/goals + commands) makes the relationship crystal clear - **Process flow**: Steps 1-5 properly sequence manifesto check → vision check → creation or display #### Potential Bugs - No functional issues found. The command maintains backward compatibility while adding new context. #### Documentation Completeness - **Output format**: Includes "Organization Context" section with manifesto reference - **Milestone descriptions**: Now show structured format (For:/Job:/Success:) which traces back to vision - **Guidelines section**: Properly distinguishes when to use /manifesto vs /vision - **Architecture repo note**: Smart addition - "If this is the architecture repo itself, use /manifesto instead" #### Style Notes - Consistent with existing command documentation format - Markdown formatting is clean and readable ### Verdict **LGTM** The hierarchy is clear, the distinction between /manifesto and /vision is well-articulated, and the output format properly references organization context. Ready to merge.

HugoNijhuis merged commit c0ef16035c into main

2026-01-07 19:25:28 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: flowmade-one/architecture#48