wa:design-document

To generate a PRD from a feature description, provide the feature or epic details to trigger a 4-stage scope-to-publish process that drafts user stories, acceptance criteria, and priorities. The output is structured product requirements written to local docs.

Yes, you can publish technical design documentation directly to Confluence. The process includes optional Confluence synchronization based on your project constants, allowing you to write architecture summaries and operational runbooks to local docs before pushing them.

The best way to create operational runbooks for system deployment is to input your system description to generate runbook documentation covering health checks, rollback procedures, and on-call guidance. It applies a stage-based review workflow to ensure operational accuracy.

BRD generation handles scope and success metrics by extracting stakeholder details, measurable success criteria, constraints, and out-of-scope items from your provided feature description. It uses configured templates to structure the business requirements document.

Yes, you need configured templates and prior design context set up before drafting business requirements. The system applies these predefined templates during its 4-stage scope-to-publish process to ensure your BRDs, PRDs, and technical docs meet YAML frontmatter metadata requirements.

A key limitation of synchronizing documentation with Confluence is that synchronization is optional and depends on predefined project constants. If these constants are not properly configured, the automated publishing stage of the documentation workflow will not execute successfully.