Accept story 36: Enforce Front Matter on All Story Files
Add POST /workflow/stories/create endpoint that auto-assigns story numbers, generates correct front matter, and writes to upcoming/. Add slugify_name and next_story_number helpers with full test coverage. Add frontend createStory API method and types. Update README to recommend creation API for agents. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,15 +0,0 @@
|
||||
---
|
||||
name: Enforce Front Matter on All Story Files
|
||||
test_plan: pending
|
||||
---
|
||||
# Story 36: Enforce Front Matter on All Story Files
|
||||
|
||||
## User Story
|
||||
As a user, I want the system to validate that every story file has valid front matter, so that story metadata (name, status, etc.) is always available to the UI and workflow engine.
|
||||
|
||||
## Acceptance Criteria
|
||||
- [ ] The workflow engine validates front matter when reading story files and reports clear errors for missing or malformed front matter.
|
||||
- [ ] Existing story files are updated to include valid front matter.
|
||||
- [ ] The TODO panel displays the story name from front matter instead of falling back to the file stem.
|
||||
- [ ] A CLI or API command can check all stories for front matter compliance.
|
||||
- [ ] A `POST /workflow/stories/create` endpoint creates a new story file with valid front matter (name, test_plan) and story scaffold, so agents never need to manually construct the file format.
|
||||
Reference in New Issue
Block a user