agentleFS
Sign inStart free
jmolzjmolz/m0lz.01/.agents/skills/source-command-create-prd/SKILL.md

source-command-create-prd

Skill0 starsChanged 6 months agoMITView on GitHub

Generate a Product Requirements Document from the current conversation

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Use this skill when the user asks to run the migrated source command create-prd.

    line 8
  2. Very specific:

    Write to: {user-provided arguments} (default: .codex/PRD.md)

    line 21
  3. Distinctive:

    If critical information is missing, ask before generating

    line 27
  4. Distinctive:

    Use this template as the output structure — fill in every section with real content from the conversation:

    line 31

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

source-command-create-prd

Use this skill when the user asks to run the migrated source command create-prd. Original argument hint: [output-path].

Command Template

Create PRD

Overview

Transform the current conversation into a structured Product Requirements Document (PRD). This captures the full scope of work for the MVP so nothing gets lost when we move to implementation.

Output

Write to: {user-provided arguments} (default: .codex/PRD.md)

Before Writing

  1. Review the ENTIRE conversation history — every detail matters
  2. Identify any assumptions you're making and flag them
  3. If critical information is missing, ask before generating

PRD Structure

Use this template as the output structure — fill in every section with real content from the conversation:

@.codex/templates/PRD-template.md

Quality Checks

Before saving, verify:

  • Every conversation detail is captured (not just the structured parts)
  • Assumptions are explicitly called out
  • MVP scope is realistic (not too ambitious)
  • Phases are granular enough for individual PICE loops
  • Out-of-scope section prevents scope creep
  • Tech stack choices are justified
  • Success criteria are measurable

After Writing

  1. Confirm the file path
  2. Summarize what's in the PRD
  3. List any assumptions that need validation
  4. Suggest reviewing the phases before starting implementation

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