scope-product-release
Installation
SKILL.md
Scope Product Release
Contract
Cut breadth, automation, polish, scale, or variants before cutting the core outcome. A smaller release must still complete a real job for a defined user. Revisit the bet when the constraint changes materially.
Workflow
- Re-state the target user, situation, must-deliver outcome, success evidence, appetite, and fixed constraints.
- Map the end-to-end journey and identify the thin coherent path that delivers value.
- Classify scope as essential outcome, trust or safety, learning instrumentation, accelerator, edge case, or future option.
- Explore reductions by segment, use case, channel, platform, geography, data type, automation, configuration, integration, scale, or service level.
- Preserve accessibility, privacy, security, compliance, reliability, supportability, rollback, and measurement at the required risk level.
- Split follow-ons by dependency and learning, not arbitrary phase labels.
- Document cuts, consequences, manual operations, upgrade path, re-entry criteria, and who accepted each tradeoff.
BuildBetter Acceleration
If BuildBetter MCP is available, search organization skills first. Use strongest customer evidence, project detail, triage, linked tickets, documents, and prior decisions to protect the core outcome and identify low-evidence scope. Do not alter project records without explicit approval.