agentleFS
Sign inStart free
irwebtoolsirwebtools/Product-Skills/skills/product/product-definition/SKILL.md

product-definition

Skill0 starsChanged 2 months agoMITView on GitHub

Create an implementation-ready product definition and scope boundary.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the task matches: product-definition, feature brief, scope.

    line 10
  2. Distinctive:

    Write a feature brief in Product language.

    line 23
  3. Distinctive:

    Keep Product validation and engineering verification distinct.

    line 38
  4. Distinctive:

    Do not claim completion without evidence.

    line 39
  5. Distinctive:

    Do not expand scope without Product confirmation.

    line 43
  6. Distinctive:

    Do not replace UX journey work.

    line 44
  7. Distinctive:

    Do not invent compliance or legal rules.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

product-definition

When to use

Use when the task matches: product-definition, feature brief, scope.

Purpose

Produce a feature brief Product and Development can execute without guessing intent.

Inputs

  • Discovery outputs
  • Known business rules and constraints

Process

  1. Write a feature brief in Product language.
  2. Capture business rules and explicit exclusions.
  3. Point to user-story and acceptance-criteria skills for detail.
  4. Confirm scope boundary before UX or coding.

Outputs

  • Feature brief
  • Scope boundary
  • Business rules summary
  • Links to stories and acceptance

Verification

  • Confirm each output exists and is reviewable.
  • Keep Product validation and engineering verification distinct.
  • Do not claim completion without evidence.

Restrictions

  • Do not expand scope without Product confirmation.
  • Do not replace UX journey work.
  • Do not invent compliance or legal rules.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free