consider

Compares viable solution options with pros, cons, and a criteria grid before implementation.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill consider-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consider
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/consider/skills/consider
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill consider-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing design decisions or implementation choices, it is easy to jump straight to the first workable solution without weighing alternatives. This Skill forces a structured comparison of viable approaches before any code is written, so tradeoffs are explicit and the user owns the final decision. ## Core Features & Use Cases - Grounded Option Generation: Explores the codebase with Glob, Grep, and Read to produce 2-4 genuinely viable options with honest pros and cons tied to real files and patterns. - Comparison Grid: Presents a side-by-side table across 5-8 relevant criteria (effort, risk, tech debt impact, reversibility) plus a key insight and blockers to resolve. - Interactive Decision and Planning: Uses AskUserQuestion to let the user choose an approach, then enters plan mode to produce a step-by-step implementation plan honoring the accepted tradeoffs. - Use Case: When deciding whether to add caching at the service layer or the database layer, the Skill explores the codebase, presents both options with tradeoffs, asks which to pursue, and plans the chosen implementation. ## Quick Start Ask the assistant to help you decide between approaches, for example: should I use Redis or in-memory caching for session storage in this service?

Frequently Asked Questions about consider

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare multiple implementation approaches before coding?

Describe the problem or decision, and the Skill explores the codebase, then presents 2-4 viable options with pros, cons, and a comparison grid. You pick an approach interactively, and it produces a step-by-step implementation plan.

What decision-making tool helps weigh tradeoffs between design options?

This Skill structures the decision by generating genuinely distinct options, scoring them across criteria like effort, risk, and reversibility, and highlighting the key differentiator. It avoids padding with weak options and flags blockers to resolve first.

Does the comparison use my actual codebase context?

Yes. For code-related problems it uses Glob, Grep, and Read to inspect relevant files, conventions, and dependencies, then grounds each option in those findings. Exploration stays minimal and targeted to what distinguishes the options.

What happens if only one approach is viable?

It presents that single option with its tradeoffs, explains why alternatives were ruled out, and asks for confirmation before planning. The comparison grid is skipped since one column offers no comparison value.

When should I not use a structured options comparison?

Skip it for trivial, unambiguous tasks where only one reasonable implementation exists and tradeoffs are negligible. The workflow adds exploration and an interactive decision step, which is overhead for mechanical changes.