agileflow-story-writer

User stories transform feature descriptions into structured 'As a... I want... So that...' format with acceptance criteria. This skill converts your requirements into actionable stories by extracting components, assigning metadata like owner and priority, generating Given/When/Then acceptance criteria, and updating project tracking automatically.

Acceptance criteria define the specific conditions a story must meet to be considered complete. They're written in Given/When/Then format to clarify expected behavior and reduce rework. This skill generates criteria automatically from your feature description, ensuring developers and QA have a shared understanding before work begins.

Yes, the skill extracts and assigns metadata including owner, priority level, and story points estimates directly from your feature input. It also updates project status indices, eliminating manual data entry and ensuring consistent tracking across your documentation and project management system.

Before finalizing a story, the skill displays a diff showing proposed changes for your approval. This validation step lets you review the extracted components, acceptance criteria, and metadata before the story is written to file, catching misinterpretations early and preventing downstream delays.

The skill writes structured story files and updates tracking indices across your documentation system. It handles end-to-end file I/O and status updates, making stories immediately actionable for development teams while keeping your project documentation synchronized.

User stories prevent vague requirements that cause rework and delays. Use them when you need to communicate feature intent to development teams clearly, especially for UI, feature, or workflow changes where understanding user benefit and success criteria upfront reduces miscommunication and accelerates delivery.