Define scope and appetite before building
conducty-shapeskillsetup L1★0
Sheshiyer/skill-clusters ↗What it does
Design scoped work with appetite, scope boundaries before planning
Best for
Medium/high-complexity goals where requirements are unclear and scope needs bounding before implementation.
Inputs
- · Goal description
- · Initial requirements or ambiguity
Outputs
- · Design doc with appetite (time budget), scope, no-go zones, approach trade-offs, approved design
Requires
- · LLM/Claude API
- · Vault/Obsidian
- · HTTP/REST API
Preconditions
- · Clear business goal
- · Stakeholder availability for questions
Failure modes
- · Appetite renegotiation mid-execution
- · Scope creep despite no-go zones
- · Design ambiguity surfaces during execution
Trust signals
- · Enforces appetite constraint (hard gate)
- · Explicitly names rabbit holes and trade-offs
- · Decomposes to sub-goals