agentleFS
simscalsimscal/sapiens-dtj/.claude/skills/product/SKILL.md

product

Skill0 starsChanged 4 months agoMITView on GitHub

Use when creating, amending, or editing `PRODUCT.md`. Owns the foundational product-context document — Vision, Core Value Proposition, Business Model, Business Goals, Target Users, Product Boundaries, Strategic Direction.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review and research.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read PRODUCT.md (absent → stop: `No PRODUCT.md found.

    line 33
  2. Very specific:

    After three failed follow-ups, offer to mark the section Not yet defined rather than write something vague.

    line 57
  3. Distinctive:

    Create asks each verbatim.

    line 127
  4. Distinctive:

    Never invent content — every body comes from interview answers or confirmed README-seeded suggestions.

    line 152
  5. Very specific:

    Never write placeholder braces ({...}) or "TBD" into the final file.

    line 153
  6. Very specific:

    Never silently overwrite an existing PRODUCT.md — always confirm.

    line 154
  7. Very specific:

    Never write skill-adjacent files (ROADMAP.md, etc.) — surface the suggestion, let the caller route.

    line 155

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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.md Authoring

Mode Detection

PRODUCT.md present?Intent verb in the requestMode
nocreate / set up / generate / init / draftCreate
yescreate / generate / regenerateConfirm: Skip (default) or Regenerate
yesrewrite / overhaul / start overConfirm: Skip (default) or Overwrite
yesamend / update / change / edit / reviseAmend
yesread-only ("what's our vision?", "show me the boundaries")Summarise; do not modify

Both destructive ops (Regenerate, Overwrite) require confirmation; Skip is the default.

Create

Confirm PRODUCT.md absent (or Regenerate/Overwrite chosen). Then:

  • Interview through the Question Bank in canonical section order — one AskUserQuestion each, applying Specificity Tests with follow-ups.
  • Surface any out-of-canon content (offer a bottom section or omit).
  • Consistency pass over all answers → resolve contradictions.
  • Author PRODUCT.md at the repo root per File Structure, concrete content.
  • Confirm with path + one-line summary per section.

Amend

Read PRODUCT.md (absent → stop: No `PRODUCT.md` found. Create it first.). Capture the full baseline verbatim — every section, subsection, non-canonical content; non-targeted sections preserved byte-for-byte. Determine target section(s) from the arg via Section Argument Map, else ask which. Offer cascade revisits (not forced):

  • Vision → Core Value Proposition, Strategic Direction
  • Target Users → Core Value Proposition, Product Boundaries
  • Business Model → Business Goals, Strategic Direction

Interview targeted section(s) → apply Specificity Tests → consistency pass against untouched baseline → rewrite per Apply Rules → overwrite PRODUCT.md → confirm section(s) updated.

Specificity Tests

Apply after every interview answer; on failure ask a focused follow-up.

General (all sections): could a new hire read this section alone and act consistently with it? If they'd ask "what did they really mean?", it fails.

SectionTest
VisionNames a specific user, problem, and outcome. "Help people be more productive" fails; "Help engineering managers run 1:1s that surface blockers earlier" passes.
Core Value PropositionNames the alternative being chosen against. "Faster checkout" fails; "Faster checkout than Shopify's default for stores with >10k SKUs" passes.
Business ModelNames who pays, what for, and roughly how much. Vague free-tier descriptions fail.
Business GoalsEach goal measurable or observable. "Improve user experience" fails; "Reduce time-to-first-value from 12 minutes to under 5" passes.
Target UsersPrimary user is a single role with named pain points, not a demographic. "Millennials" fails; "Solo founders in their first year, juggling sales and product" passes.
Product BoundariesIn/Out of Scope each have a concrete example. "Various integrations" fails; "Stripe, Slack, Linear at launch — no Salesforce, no Microsoft stack" passes.
Strategic DirectionNames 1–2 priorities and one explicit non-priority. "Grow the platform" fails; "Q3: depth in analytics over breadth of integrations. Not chasing mobile parity this year." passes.

After three failed follow-ups, offer to mark the section Not yet defined rather than write something vague.

Contract

File Structure

Pure markdown — no frontmatter, no version field. Seven canonical sections in immutable order:

# Product Context

## Vision

{vision statement — one clear paragraph}

## Core Value Proposition

{single clearest reason a customer chooses this product over alternatives — one sentence or short paragraph}

## Business Model

{how the product makes money — one short paragraph}

## Business Goals

{each goal as a bullet point}

## Target Users

### Primary: {primary persona name or role}

{description of role, key needs, and pain points}

### Secondary: {secondary persona name or role}

{description — omit this subsection entirely if no secondary users were identified}

## Product Boundaries

### In Scope

{each in-scope capability as a bullet point}

### Out of Scope

{each exclusion as a bullet point — or "Not specified" if none given}

## Strategic Direction

{strategic direction as a paragraph; name 1–2 priorities and at least one explicit non-priority}

Non-canonical user-added sections, if any, appear at the bottom and are preserved untouched on amend.

Section Argument Map

ArgumentSection
visionVision
value or propositionCore Value Proposition
modelBusiness Model
goalsBusiness Goals
usersTarget Users
boundariesProduct Boundaries
strategy or directionStrategic Direction
allAll sections
Comma-separated list (e.g. vision,value)Multiple sections

Interview Question Bank

Create asks each verbatim; Amend prefixes "the updated" or "now" where natural.

SectionQuestion
Vision"What is the product vision? Describe the problem it solves, for whom, and the core value it delivers."
Core Value Proposition"What is the core value proposition? The single clearest reason a customer chooses this product over alternatives — name the alternative."
Business Model"What is the business model? How does the product make money — who pays, what for, and roughly what's the price shape?"
Business Goals"What are the 3–5 key business goals? List them as short, action-oriented, measurable statements (e.g. 'Grow monthly active users to 50k', 'Reduce average checkout time below 30s')."
Target Users"Who are the target users? Describe the primary user as a specific role with named pain points. Include a secondary user if applicable."
Product Boundaries"What is explicitly in scope for this product at launch? What is explicitly out of scope — even if it might seem like an obvious fit?"
Strategic Direction"What is the current strategic direction? Name the 1–2 priorities for the next quarter or two, and at least one explicit non-priority — something you're choosing not to pursue."

Apply Rules

  • Create writes the file end-to-end via File Structure. Every section gets concrete content — no placeholders, {…} braces, "TBD".
  • Amend edits only targeted section(s); non-targeted sections preserved byte-for-byte (headings, paragraphs, bullets, subsections, bottom non-canonical sections). Target all → rewrite all seven canonical sections, preserve non-canonical. Single section → rewrite only its body (+ subsections), leave heading unchanged.
  • Specificity Test failing after three follow-ups + user agrees → write Not yet defined. as the section body.

Constraints

  • Section order is immutable — seven sections in the File Structure order.
  • Section headings match canonical names exactly.
  • ### Secondary: omitted entirely when no secondary user exists — no empty heading.
  • ### Out of Scope falls back to Not specified only when asked and explicitly given none.
  • PRODUCT.md is pure markdown — no YAML frontmatter, version field, or metadata block.
  • Never invent content — every body comes from interview answers or confirmed README-seeded suggestions.
  • Never write placeholder braces ({...}) or "TBD" into the final file.
  • Never silently overwrite an existing PRODUCT.md — always confirm.
  • Never write skill-adjacent files (ROADMAP.md, etc.) — surface the suggestion, let the caller route.
  • Filesystem: write only PRODUCT.md.

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.