Identify deliberate trade-offs to prevent scope creep during planning and reviews.
npx skills add https://github.com/ReviewStage/stage-cli --skill trade-off
Please help me install this Agent Skill. Skill: trade-off Source: https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/trade-off Command: npx skills add https://github.com/ReviewStage/stage-cli --skill trade-off
Surface explicit, high-impact trade-offs to prevent complexity creep and over-engineering during planning, pre-implementation, or post-diff reviews.
Propose the top three trade-offs for the current task and explain the rationale in plain terms.
High-intent search queries and answers about installing and using this skill.
Preventing scope creep during architecture planning requires identifying deliberate trade-offs that surface behavior-level and architecture-level cuts. This produces concrete reductions and rationale to prevent over-engineering before implementation begins.
Architectural trade-offs in decision-making are explicit choices to reduce infra and maintenance complexity, such as cutting queues, caches, or services. They articulate the scope and justification for each cut to align engineering decisions without breaking intent.
Reviewing code diffs for over-engineering involves applying deliberate trade-offs after evaluating changes that touch user-facing behavior and architectural design. You identify explicit cuts and provide actionable decisions to streamline features and reduce infra complexity.
You need to evaluate trade-offs for feature scoping across three moments: during planning, before implementation, and after reviewing diffs. This ensures high-impact complexity reductions are identified and aligned across product, design, and engineering.
You can streamline user-facing flows without breaking product intent by identifying behavior-level reductions as deliberate trade-offs. This provides clear justification and scope for each cut to align design and engineering decisions effectively.
2good4meAnalyze requirements, evaluate trade-offs, and document architectural decisions in ADR format.
MatheusBBarniExamine project plan assumptions and update CONTEXT.md and ADRs inline.
pauljbernardModels enterprise risk management frameworks including COSO ERM and ISO 3100 compliance.
atholaScore feature worthiness and enforce branch size constraints during planning.
