agentleFS
agentmartagentmart/pm-os/.claude/skills/review-launch/SKILL.md

review-launch

Skill1 starsChanged 7 months agoMITView on GitHub

Trigger all 7 specialist reviewers to critique a launch plan.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read each sub-agent persona file and produce a review from that perspective:

    line 7
  2. Very specific:

    Read sub-agents/engineer-reviewer.md → produce the Engineer review

    line 9
  3. Very specific:

    Read sub-agents/designer-reviewer.md → produce the Designer review

    line 10
  4. Very specific:

    Read sub-agents/exec-reviewer.md → produce the Executive review

    line 11
  5. Very specific:

    Read sub-agents/user-researcher.md → produce the User Researcher review

    line 12
  6. Very specific:

    Read sub-agents/data-analyst.md → produce the Data Analyst review

    line 13
  7. Very specific:

    Read sub-agents/legal-reviewer.md → produce the Legal/Privacy review

    line 14
  8. Very specific:

    Read sub-agents/competitor-watcher.md → produce the Competitor Watcher review

    line 15
  9. Very specific:

    Read sub-agents/debate-facilitator.md → run a debate pass across the 7 reviews, surfacing the sharpest tensions and agreements between …

    line 16
  10. Very specific:

    Read sub-agents/synthesis-agent.md → produce the final weighted recommendation with explicit must-fix / should-fix / consider buckets

    line 17

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

Read each sub-agent persona file and produce a review from that perspective:

  1. Read sub-agents/engineer-reviewer.md → produce the Engineer review
  2. Read sub-agents/designer-reviewer.md → produce the Designer review
  3. Read sub-agents/exec-reviewer.md → produce the Executive review
  4. Read sub-agents/user-researcher.md → produce the User Researcher review
  5. Read sub-agents/data-analyst.md → produce the Data Analyst review
  6. Read sub-agents/legal-reviewer.md → produce the Legal/Privacy review
  7. Read sub-agents/competitor-watcher.md → produce the Competitor Watcher review
  8. Read sub-agents/debate-facilitator.md → run a debate pass across the 7 reviews, surfacing the sharpest tensions and agreements between reviewers
  9. Read sub-agents/synthesis-agent.md → produce the final weighted recommendation with explicit must-fix / should-fix / consider buckets

Focus critique on launch readiness, rollout risk, and GTM gaps.

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.