agentleFS
Sign inStart free
websublimewebsublime/mister-anderson/skills/manifesto/SKILL.md

manifesto

Skill3 starsChanged 7 months agoMITView on GitHub

Guide the creation of a product manifesto — vision, principles, and governing laws that shape all downstream decisions.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides $ARGUMENTS, analyze them for:

    line 14
  2. Distinctive:

    Check if a manifesto already exists:

    line 18
  3. Very specific:

    Search for docs/MANIFESTO.md or MANIFESTO.md

    line 19
  4. Distinctive:

    If found, ask the user: "A manifesto already exists at {path}.

    line 20
  5. Distinctive:

    No strict prerequisites — the manifesto is the first artifact in the pipeline.

    line 24
  6. Distinctive:

    If a PRD already exists but no manifesto:

    line 26
  7. Very specific:

    Ensure the docs/ directory exists (create if needed)

    line 33
  8. Distinctive:

    Update status to APPROVED </on-execute>

    line 71
  9. Distinctive:

    Verify the manifesto file was created at the agreed path

    line 75

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

Manifesto

Guide the user through defining the product's vision, principles, and governing laws. The manifesto is the foundation that PRD, architecture, and all downstream documents reference.

<on-init> If the user provides $ARGUMENTS, analyze them for: - A product name or concept - An existing manifesto path to review/iterate

Check if a manifesto already exists:

  • Search for docs/MANIFESTO.md or MANIFESTO.md
  • If found, ask the user: "A manifesto already exists at {path}. Do you want to review and iterate on it, or start fresh?"</on-init>
<on-check> No strict prerequisites — the manifesto is the first artifact in the pipeline.

If a PRD already exists but no manifesto:

  • Inform: "A PRD exists but no manifesto was found. The manifesto defines the governing principles that the PRD should align with. Creating it now will provide a foundation for reviewing the PRD."</on-check>
<on-execute> 1. **Define output location:** - Suggest default: `docs/MANIFESTO.md` - Ensure the `docs/` directory exists (create if needed)

  1. Guide the user through these sections:

    Vision — What does this product exist to do? One sentence.

    Principles — 3-7 guiding principles that shape every decision. Example: "GitHub stores, Rust computes — zero custom storage"

    Governing Laws — Non-negotiable rules. If a design violates a law, the design is wrong. Example: "Every write invalidates and recomputes — consistency after mutations"

    Out of Scope — What this product will never do. Explicit boundaries.

  2. Write the manifesto to the agreed path using this structure:

    # {Product Name} — Manifesto

**Status:** DRAFT | APPROVED
**Date:** {date}

## Vision
{one sentence}

## Principles
1. {principle} — {why}
2. ...

## Governing Laws
1. {law} — {consequence if violated}
2. ...

## Out of Scope
- {what this product will never do}
  3. Iterate with the user until they approve
  4. Update status to APPROVED</on-execute>
<on-complete> 1. Verify the manifesto file was created at the agreed path 2. Show the user the status (DRAFT or APPROVED) </on-complete><on-complete if="status=DRAFT"> Inform the user they can continue editing the manifesto directly or re-run `/manifesto` to iterate. </on-complete><on-next> Recommend proceeding with `/requirements` to create the PRD, referencing the manifesto as the governing document. </on-next>

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