Decompose sprint targets into a deterministic Task Queue with per-task analyses.
npx skills add https://github.com/adaw/skills --skill fabric-analyze
Please help me install this Agent Skill. Skill: fabric-analyze Source: https://github.com/adaw/skills/tree/main/fabric-analyze Command: npx skills add https://github.com/adaw/skills --skill fabric-analyze
This Skill transforms high-level sprint targets into a detailed, actionable Task Queue, ensuring every task is precisely defined with necessary analyses and constraints before implementation begins.
Use the fabric-analyze skill to convert sprint targets into a detailed task queue with per-task analyses.
High-intent search queries and answers about installing and using this skill.
Agile task decomposition is the process of breaking down sprint targets into a deterministic Task Queue. It ensures implementation readiness by defining data flow, module dependencies, entity lifecycles, and test strategies for each granular task.
Agile task decomposition is the process of breaking down sprint targets into a deterministic Task Queue. It ensures implementation readiness by defining data flow, module dependencies, entity lifecycles, and test strategies for each granular task.
Enforce governance during sprint planning by cross-referencing decomposed tasks with ADRs and specs. This process flags architectural conflicts and escalates them via intake items to maintain explicit governance constraints before development begins.
Yes, you can generate per-task analyses for individual stories. This process produces detailed definitions for data flow, module dependencies, and test strategies, ensuring every decomposed task is fully specified and ready for developers.
The best way to define module dependencies and data flow is through per-task analysis during task decomposition. This approach explicitly maps entity lifecycles and architectural constraints for each task before implementation starts.
You should escalate spec conflicts in a task queue when decomposed tasks contradict existing ADRs or specs. Governance enforcement identifies these conflicts and routes them as intake items for resolution prior to implementation.
zerAdaDecompose product requirements documents into structured epics and user stories.
riezDispatch specialized agents for independent tasks with two-stage reviews.
tja688Cross-reference project plans against CONTEXT.md and ADR files.
jason-hchsiehDecompose high-level requirements into phased task plans with dependencies.
