Feature Intake Triage

Evaluate any feature request with structured scoring and a Build / Investigate / Defer / Decline decision.

Install
cmdop skills install agensi-feature-intake-triage

Feature Intake Triage is a Claude Code skill that runs any incoming feature request through a repeatable evaluation framework. It accepts raw input in whatever form it arrives — an email thread, a Slack message, a meeting note, or a verbal description — and extracts five key dimensions: the problem being solved, the user affected, the value delivered, the estimated effort, and known alternatives.

Once those dimensions are extracted, the skill scores the request across four axes — Problem clarity, User impact, Strategic fit, and Feasibility — each contributing to a total score out of 20. Any assumptions made during scoring are flagged explicitly so reviewers know where the analysis is uncertain.

The output is one of four triage decisions: Build, Investigate, Defer, or Decline. Each decision comes with a recommended next step. When the decision is Decline, the skill also generates a suggested response to send back to the requester.

The skill installs as a SKILL.md file inside a Claude Code project. It activates when phrases such as “evaluate this request”, “should we build this”, “triage this idea”, “a customer asked for”, or “new feature request” appear in a conversation. No environment variables or external services are required. It is appropriate for product teams that want a consistent, documented evaluation process for inbound feature requests handled inside Claude Code.

Use cases

  • Score an inbound customer feature request from a support email to decide whether to build it
  • Triage a backlog of Slack-captured feature ideas into Build, Investigate, Defer, or Decline buckets
  • Generate a structured decline response to send back to a requester when a feature is out of scope
  • Flag unclear assumptions in a verbal feature description before it reaches engineering
  • Apply a consistent 20-point scoring rubric across all feature requests reviewed in a sprint

When to use it

  • When a product team wants a structured, repeatable triage process for feature requests inside Claude Code
  • When feature requests arrive as unstructured text and need key dimensions extracted before evaluation
  • When the team needs an audit trail of scores and assumptions for each request reviewed
  • When a written response to a declining requester is needed quickly

When not to use it

  • Outside of Claude Code — this skill requires a Claude Code project environment
  • When the team needs integration with an external issue tracker or product management tool
  • When evaluation criteria differ significantly from the four built-in axes (Problem clarity, User impact, Strategic fit, Feasibility)
  • When automated bulk import of many requests at once is required rather than conversational triage