Challenge and critically evaluate this feature idea before any implementation: **$ARGUMENTS**
Challenge and critically evaluate this feature idea before any implementation: $ARGUMENTS
/spec Quick Triage recommends it (high complexity detected)/spec directly/research instead/explore instead/specSummarize the proposed feature in 1-2 sentences in your own words to confirm understanding.
Read .agents/context/CONCEPT.md now. If the file does not exist, skip the concept fit check entirely and note "No CONCEPT.md found — concept fit check skipped." Otherwise, evaluate:
.agents/context/CONCEPT.md?Rate concept fit: ALIGNED / BORDERLINE / MISALIGNED (skip if CONCEPT.md missing)
Is this actually needed? Challenge it hard:
List 1-3 alternatives, including:
Also scan the codebase with Glob and Grep to check if similar functionality already exists.
Simulate the following viewpoints. Skip any perspective that is clearly not applicable (e.g. skip UX for a CLI-only backend change — state "N/A" with a one-line reason).
Security Engineer — Does this introduce attack surface, data exposure, or trust boundary issues? Are there auth, input validation, or secrets-handling concerns?
UX Designer — Does this affect the user-facing experience or discoverability? Is the interaction model consistent with existing conventions? Could it confuse or overwhelm users?
DevOps Engineer — Does this impact deployment, CI/CD, environment config, or observability? Are there operational risks (rollback difficulty, missing metrics, config drift)?
End User — Does this solve a problem the user actually has? Is it discoverable without reading docs? Could it cause unintended side effects the user would not expect?
Choose exactly one. Incorporate concerns raised in Phase 6b into the rationale.
GO — Concept fits, clearly needed, manageable complexity. Recommend proceeding.
SIMPLIFY — The idea has merit but the proposed scope is too large. State the smaller version worth building.
REJECT — Misaligned with concept, unnecessary, or adds unjustified overhead. State the reason explicitly.
.agents/context/CONCEPT.md when evaluating concept fit (only if file exists)./spec (GO/SIMPLIFY) or shelve (REJECT). Do not re-challenge the same idea — diminishing returns after the first pass./spec "task description" to create a structured implementation plan./spec "reduced scope" with the agreed-upon smaller scope.