solution-shaping
1
总安装量
1
周安装量
#76694
全站排名
安装命令
npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill solution-shaping
Agent 安装分布
amp
1
cline
1
opencode
1
cursor
1
kimi-cli
1
codex
1
Skill 文档
Solution Shaping
Shape source material into an Interaction Tree and State Model â a story map and domain model. Contains 11 rules across 4 categories to guide shaping of requirements into epics, sub-epics, and stories with associated state concepts.
When to Apply
Reference these guidelines when:
- Shaping requirements from source documents into a story map
- Deriving epics and stories from user journeys or business flows
- Building an Interaction Tree (hierarchical actor exchanges)
- Modeling domain state concepts (State Model)
- Defining story granularity and slice order
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Source & Scope | HIGH | source- |
| 2 | Hierarchy | HIGH | hierarchy- |
| 3 | State & Structure | HIGH | state- |
| 4 | Interaction | MEDIUM-HIGH | interaction- |
Quick Reference
1. Source & Scope (HIGH)
source-derive-from-sourceâ Derive concepts from interactions in the source; do not invent workflowssource-logical-domain-levelâ Keep at logical/domain level; no implementation detailssource-speculation-assumptionsâ State assumptions when unclear; do not speculate or invent
2. Hierarchy (HIGH)
hierarchy-parent-granularityâ Keep parent nodes at appropriate granularity; do not leak child detailhierarchy-sequential-orderâ Order tree sequentially; required state creators before consumers
3. State & Structure (HIGH)
state-required-stateâ Shared state on parent only; comprehensive preconditionsstate-resulting-stateâ Same inheritance as required state; outcome language onlystate-failure-modesâ Max 3 per interaction; domain rules onlystate-concept-scopingâ Scope concepts to Epic/Story that owns themstate-structured-conceptsâ Complete full workflow (interactions â concepts â State Model) for each slice
4. Interaction (MEDIUM-HIGH)
interaction-supporting-actor-responseâ Supporting = system; Actor â System exchangeinteraction-story-granularityâ Break down by distinct areas; sufficient stories for rule detail
How to Use
Read individual rule files for detailed DO/DO NOT guidance:
rules/source-derive-from-source.md
rules/state-required-state.md
Each rule file contains:
- Brief explanation
- DO with example
- DO NOT with example
Full Compiled Document
For the complete guide with all rules, core definitions, output structure, validation, and shaping process: AGENTS.md
Build
To regenerate AGENTS.md from rules and content:
python scripts/build_agents_md.py
Run from the solution-shaping skill directory.