requirements-engineering

To generate epics and features, provide your business analysis input under the _devprocess/analysis/BA-*.md path. The skill processes these BA inputs to automatically create structured epics, features, and backlog items with enforced frontmatter discipline.

An architect handoff document translates business requirements into architectural planning artifacts. The skill automatically generates an architect-handoff.md file from your BA inputs, ensuring a consistent bridge between analysis and architecture.

Backlog synchronization happens automatically when the skill generates new epics and features from your BA inputs. It enforces backlog governance by keeping Epic, Feature, and ADR links updated and aligned with defined templates.

Yes, this skill is designed specifically for PoC and MVP scoping using BA inputs and related exploration data. It transforms these inputs into structured backlog items and ready-to-hand-off architectural artifacts.

Yes, the skill enforces strict frontmatter rules when generating epics and features from your analysis documents. This discipline ensures consistent metadata structure across all generated backlog items and handoff artifacts.

The best way to bridge BA output to architecture is to transform analyses into structured epics, features, and handoff documents. This skill automates that translation, ensuring measurable requirements and ready-to-hand-off artifacts for architectural planning.