harness-create-story

To generate developer-ready story context, you must resolve workflow customizations and load PRD, architecture, and UX artifacts. This produces an exhaustive story file containing requirements, guardrails, and validation proof expectations for reliable AI feature development.

AI agents lack project context when story files omit prior-work history and architecture constraints. Generating a dedicated story file prevents omissions by extracting code-change scope, analyzing prior commits, and applying template-driven construction with implementation guardrails.

To create a story for sprint planning, ask your agent to target an epic-story path identifier like 'create story 1-2-user-auth'. The workflow finalizes sprint-status and moves the generated story into a ready-for-dev state for immediate development.

Template-driven story construction is the process of building an implementation guide using required file-path conventions. It ensures the AI agent applies exhaustive artifact analysis to preserve regressions and includes complete product and UX context.

Yes, story generation loads existing markdown templates and integrates architecture analysis. The workflow-driven discovery reads previous stories and extracts code-change scope to ensure the generated developer-ready spec aligns with your current project structure.

Automated sprint integration requires existing PRD, epics, and UX artifacts to function correctly. Without these prerequisites, the story context engine cannot perform exhaustive artifact analysis or establish the implementation guardrails needed to prevent development disasters.