Update /vision command for product-level only #41

New Issue

HugoNijhuis · 2026-01-07T18:51:54Z

HugoNijhuis commented

2026-01-07 18:51:54 +00:00

Summary

Update the /vision command to be product-level only. It should reference the organization manifesto but manage product-specific vision, personas, jobs, and milestones.

Changes

Scope: Product-level only (not organization)
Reference: Should mention/link to org manifesto when displaying
Inheritance: Product personas/jobs can extend org-level ones
Milestones: Remain at product level in Gitea

Updated Behavior

Check for manifesto: Note if org manifesto exists (in architecture repo)
Check for vision.md: Product-level vision in current repo
If no vision: Guide through product vision creation (referencing manifesto)
If vision exists: Display with manifesto reference

Output Format

## Organization Context
See manifesto: [link or reference to architecture/manifesto.md]

## Product: [Name]

### Who This Product Serves
[Product-specific personas, may extend org personas]

### Product Jobs to Be Done
[Product-specific jobs]

### Goals (Milestones)
| Goal | For | Progress |
|------|-----|----------|

Dependencies

Depends on #38 (manifesto must exist to reference)

Acceptance Criteria

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

## Summary Update the `/vision` command to be product-level only. It should reference the organization manifesto but manage product-specific vision, personas, jobs, and milestones. ## Changes 1. **Scope**: Product-level only (not organization) 2. **Reference**: Should mention/link to org manifesto when displaying 3. **Inheritance**: Product personas/jobs can extend org-level ones 4. **Milestones**: Remain at product level in Gitea ## Updated Behavior 1. **Check for manifesto**: Note if org manifesto exists (in architecture repo) 2. **Check for vision.md**: Product-level vision in current repo 3. **If no vision**: Guide through product vision creation (referencing manifesto) 4. **If vision exists**: Display with manifesto reference ## Output Format ``` ## Organization Context See manifesto: [link or reference to architecture/manifesto.md] ## Product: [Name] ### Who This Product Serves [Product-specific personas, may extend org personas] ### Product Jobs to Be Done [Product-specific jobs] ### Goals (Milestones) | Goal | For | Progress | |------|-----|----------| ``` ## Dependencies - Depends on #38 (manifesto must exist to reference) ## Acceptance Criteria - [ ] /vision command updated for product-level scope - [ ] References organization manifesto - [ ] Clear distinction from /manifesto command - [ ] Works in product repos (not architecture repo)

HugoNijhuis referenced this issue

2026-01-07 18:52:27 +00:00

Rename repo from 'ai' to 'architecture' #44

HugoNijhuis added a new dependency 2026-01-07 18:52:39 +00:00

#38 Create manifesto.md for organization vision

HugoNijhuis added a new dependency 2026-01-07 18:52:40 +00:00

#44 Rename repo from 'ai' to 'architecture'

HugoNijhuis referenced this issue

2026-01-07 18:52:51 +00:00

Consider renaming repo to 'architecture' to include engineering patterns #37

HugoNijhuis referenced this issue from a commit

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