agentleFS
Sign inStart free
fusebase-devfusebase-dev/fusebase-flow/.agents/skills/product-docs-first/SKILL.md

product-docs-first

Skill9 starsChanged 27 days agoMITView on GitHub

Use when starting a new app and the operator wants product documentation designed before code, OR docs/<app>/product.md exists. Ingests operator research and the North Star, then designs per-app product docs that planning builds from. If no product.md exists and the operator did not ask to create one, this skill does nothing (silent no-op) — do NOT auto-create. Not for mid-implementation edits.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Gate: If no docs/<app>/product.md and no operator request to create one → exit silently.

    line 50
  2. Distinctive:

    Do not auto-create product docs unprompted.

    line 78
  3. Distinctive:

    Do not write code (FR-01) — this designs the product, not the implementation.

    line 79
  4. Distinctive:

    Do not invent product intent the operator didn't supply.

    line 80

≈ “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 Docs First

Style: Mode-B-lite. Artifact-gated — acts only when docs/<app>/product.md exists or the operator asks to create one.

Purpose

Design product documentation per app before writing code, so planning and implementation build from a clear product intent instead of guessing. Ingests operator research and the North Star (if present).

When to invoke

  • Operator starts a new app and says "design the product docs first", "write product documentation", "what should this app do".
  • docs/<app>/product.md already exists (read it to ground planning).
  • Operator dropped research in docs/<app>/research/ and asks to turn it into product docs.

Do not invoke when

  • No docs/<app>/product.md AND the operator did not ask to create one → silent no-op; do not auto-create.
  • Mid-implementation edits (planning already done).
  • Small bug fixes, refactors, copy-only changes, narrow technical tickets, or already-scoped implementation work with no long-lived product-intent change → do not expand product docs (FR-23 / flow-skills/documentation-budget/SKILL.md).

Required inputs

InputWhere it livesIf missing
Product intent (operator answers)chatask in chat (FR-19); do not invent
Research (optional)docs/<app>/research/proceed without; note it
North Star (optional)docs/north-star.mdproceed; align if present
Templatetemplates/product.mdstop; template missing

Procedure

  1. Gate. If no docs/<app>/product.md and no operator request to create one → exit silently.
  2. Ingest any research + the North Star; summarize, cite, never invent domain facts.
  3. Design the product doc from templates/product.md: purpose, users, core jobs, key screens/flows, data, the apps this product breaks into (feeds product-apps-decomposition), non-goals.
  4. Write docs/<app>/product.md with last_updated today (only operator-provided content).
  5. Hand to planning (implementation-planning) grounded in the product doc.
  6. Ambiguity → ask operator (FR-19).

Output artifacts

ArtifactPathMode
Product docdocs/<app>/product.mdMode B

Failure cases

FailureDetectionResponse
Artifact absent + no requeststep 1silent no-op
Vague product intentcan't fill sectionscapture only what's given; no fabrication
Template missingstep 4stop; report missing templates/product.md

Escalation path

  • Domain expertise needed → skill-authoring (domain-expert mode).
  • Vision conflict → north-star / ask operator (FR-11).

Anti-patterns

  • Do not auto-create product docs unprompted.
  • Do not write code (FR-01) — this designs the product, not the implementation.
  • Do not invent product intent the operator didn't supply.

Clean-room note

Original Fusebase Flow content. See docs/source-map.md. No third-party code, prompts, or skill files copied.

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