agilebydesign/abd-shaping
backup/abd-shaping/SKILL.md
Shape source material into an Interaction Tree and State Model (story map and domain model). Use when shaping requirements, deriving epics and stories from source documents, or building a hierarchical structure of actor exchanges and domain concepts.
development
Updated Mar 27, 2026
$ install --global
skillsauthnpx skillsauth add agilebydesign/agilebydesign-skills abd-shapingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 29, 2026, 8:24 AM36.6s34 files scanned
SKILL.md
- name:
- abd-shaping
- description:
- Shape source material into an Interaction Tree and State Model (story map and domain model). Use when shaping requirements, deriving epics and stories from source documents, or building a hierarchical structure of actor exchanges and domain concepts.
- license:
- MIT
- author:
- agilebydesign
- version:
- 1.0.0
Ace-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.
Source Folder Structure
abd_content/source/ contains content sources. Workspace RFQ folders are linked in for skill access:
source/JBOM Agile Support— Junction toworkspace/Scotia Talent Journey Based Operating Model/source(RFQ docs, B&T, Supplier Q&A, etc.)
Use this path when shaping from RFQ or JBOM source material.
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 content:
cd skills/abd-shaping
python scripts/build.py
Run from the agilebydesign-skills root, or from within the abd-shaping skill directory.
Related Skills
agilebydesign/abd-maps-models-specs
development
VerifiedTrustedCommunity
Synthesizes a map-model-spec (domain model + story map) from chunked context. Pipeline: context (Stages 1–3) then map-and-model steps per parts/process.md (scaffold, classify, deepen, integrate, evidence, structure, finalize). Use when the user wants to "synthesize map model spec", "build story map from context", or "extract domain and stories from chunks".
SKILL.mdUpdated Apr 10, 2026
agilebydesign/agile-skill-build
development
VerifiedTrustedCommunity
Agile Skill Build — Create and scale ace-skills. Scaffold new skills and assemble content into AGENTS.md. Use when creating or scaling a skill with the standard ace-skill structure.
SKILL.mdUpdated Mar 27, 2026
agilebydesign/skills/ace-foo
development
VerifiedTrustedCommunity
# ace-foo Ace-skill. Fill content pieces and run build.
SKILL.mdUpdated Mar 27, 2026
agilebydesign/abd-synthesis-orchestrator
development
VerifiedTrustedCommunity
Drives the synthesis workflow (create_strategy, run_slice, validate) using abd-story-synthesizer. Use when running orchestrated story synthesis, shaping content into interaction tree and state model, or when the user asks to run the synthesis orchestrator.
SKILL.mdUpdated Mar 27, 2026