Skip to content

Product Direction Judge

Judges feature requests against a repo's written product direction and records each no with evidence

Repository
prisma/orm
Stars
47,663
Licence
Apache-2.0
Files
8 files

What it does

Once installed, the agent checks feature requests, feature pull requests and its own feature proposals against the project's written vision, intent and decision records before reviewing code. It returns a verdict (aligned, rejected, unclear or not applicable) with a quoted line as evidence, and is told to leave the final decision to a maintainer. It also helps set up the pages that hold this direction, such as a project intent page, vision page, decision records and a steering list.

Great for

  • Maintainers of open source projects who want consistent, cited answers when triaging feature requests
  • Contributors who want to check whether a feature idea fits the project before writing code
  • Teams setting up written product direction, decision records or an ADR index

Skip it if

  • Bug reports or routine code review, where the skill itself says a direction judgment means nothing (it returns not_applicable)
  • Repositories with no written direction pages: the skill reports missing parts as unknown, so verdicts will mostly be unclear, and it does not invent direction
  • Fully autonomous rejection of user requests: the skill says a wrong no drives people away, so declines need grounds and a maintainer decision

Try asking

  • “Triage this feature request against the project's vision and steering list and give me a cited verdict”
  • “Does this pull request adding a new config option fit the project's direction?”
  • “Set up a project intent page and a steering list for this repository”
  • “Record this maintainer decision as a decision record and add it to the steering list”
Step-by-step guide: how to use Product Direction JudgeInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 8 original files, the Apache-2.0 licence and an attribution note.

    product-direction.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip product-direction.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip product-direction.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Make sure the repository's AGENTS.md or CLAUDE.md points to the project intent, vision and steering list so the agent finds them quickly
  • Treat verdicts as advice: check the cited anchor yourself before acting, especially any proposed decline
  • Ask a maintainer to accept or delete any Proposed decision records, since the skill ignores them as grounds

What's inside

  • assets/decision-record.md
  • assets/project-intent.md
  • assets/steering-list.md
  • assets/vision.md
  • references/maintaining.md
  • references/sources.md
  • references/worked-example.md
  • SKILL.md

Redistributed unmodified from prisma/orm under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.