Requirement Decompose
When to use
Customer uploaded Word/PDF/MD materials need structured breakdown before design or development.
Output contract
Write output/<task_id>/requirement-breakdown.md with sections:
- Source materials — list absolute paths ingested
- Functional pages — numbered routes/components
- Interactions — primary user flows
- Acceptance criteria — checkbox list, testable
- Out of scope — explicit non-goals
- Reuse hints — components/skills from AgenticX core worth reusing
Process
- Run
knowledge_searchif KB auto-retrieval is enabled - Cross-check against
sample-rfp.mdpatterns for enterprise portal POCs - Keep MVP scope minimal — flag anything needing customer sign-off
Quality bar
- Every acceptance item maps to at least one page or flow
- No placeholder "TBD" in acceptance section