-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Labels
area: prdPRD generation and conversionPRD generation and conversionenhancementNew feature or requestNew feature or requestpriority: highBlocks users or degrades experienceBlocks users or degrades experiencesize: mediumA few files, clear scopeA few files, clear scope
Description
Context
Users sometimes edit prd.md directly (via vim, Claude, etc.) and want the JSON to reflect those changes. The current workflow for regenerating JSON from an edited markdown file is unclear and error-prone.
Problem
- No clear way to regenerate
prd.jsonfrom an editedprd.md chief edit <name>followed by immediately exiting Claude can produce incomplete JSON (see related merge/truncation bugs)- Users have to guess the workflow: edit md →
chief edit→ exit → hope conversion works - The docs at chiefloop.com/concepts/prd-format.html don't cover this workflow
Suggested solution
- Detect drift: Chief could notice when
prd.mdhas been modified more recently thanprd.jsonand prompt to rebuild - CLI command:
chief rebuild <name>orchief sync <name>to programmatically regenerate JSON from markdown without going through Claude - Document the workflow on the PRD format docs page
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: prdPRD generation and conversionPRD generation and conversionenhancementNew feature or requestNew feature or requestpriority: highBlocks users or degrades experienceBlocks users or degrades experiencesize: mediumA few files, clear scopeA few files, clear scope