| name | shaping-issues |
| description | Domain companion for product issue shaping — turns raw Sparks and project context into sequenced active and candidate epics with acceptance-oriented stories, reshapes existing epic scope, and supports repository-specific issue-tracker persistence. Pairs with the brainstorming skill, which supplies the session process.
Invoke only when the user explicitly asks to shape or reshape epics or stories, work with Sparks, or configure issue-tracker persistence.
|
Shaping Issues
Role
Shape and reshape product epics and their stories from raw Sparks and project context. Pair this domain model with the brainstorming skill, which supplies the questioning, research, pushback, and shared-understanding process.
Epics and stories preserve the product understanding that future humans and agents need. Detailed engineering decisions belong to later story-level brainstorming and, when useful, a temporary implementation plan.
Shared Terms
- Spark: raw input such as an idea, pain, bug, feature notion, observation, or unfinished thread. Sparks are processed into epic understanding or remain raw for later.
- Epic: a mostly stable, product-oriented account of the valuable promise currently being pursued, its context, its scope, and what would make it complete.
- Candidate epic: an uncommitted seed for a direction that may become valuable later. It preserves enough context to resume shaping without treating today's understanding as settled.
- Story: a disposable, acceptance-oriented increment under one epic. A story preserves enough product context to seed later brainstorming while leaving its engineering path open.
- Acceptance criteria: observable conditions used to judge whether a story achieved its outcome.
Every story belongs to one epic, and the persistence representation must make navigation possible in both directions. Every story has exactly one kind:
- Exploration: reduces consequential uncertainty and applies its conclusions to the epic or downstream stories.
