story-craftsman

To write INVEST-compliant user stories with verifiable acceptance criteria, use a structured interview protocol to extract requirement context like background, goals, and quantifiable success metrics. This eliminates vague requirements by generating standardized documents with clear acceptance criteria.

The best way to initialize a standardized project documentation directory structure is to generate the full 5-folder standard hierarchy with .gitkeep files and maintenance guidelines. This ensures consistent documentation organization across teams for new projects.

Automated document placement for user stories works by inferring the target project sub-module from file paths or git status. It then saves generated requirement documents into standardized module-specific directories like docs/04-user-stories/, avoiding manual file organization errors.

Yes, you can fix incomplete requirement documentation before development by applying a guided generation process. It clarifies pain points and quantifiable metrics, producing standardized user story documents that prevent requirement misalignment and wasted development time.

Generating user stories requires no specific dependencies. The skill operates independently within software development and product management environments to produce standardized requirement documentation and initialize project docs.

The limitation of using structured interview protocols for requirement documentation is that it requires stakeholders to provide clear background context and quantifiable goals. Without active stakeholder input to clarify missing requirements, the generated user story may lack the necessary verifiable acceptance criteria.