agentleFS
lza6lza6/claw-code-tingfeng/skills/ralph-init/SKILL.md

ralph-init

Skill5 starsChanged 12 days agoMITView on GitHub

Initialize a PRD (Product Requirements Document) for structured ralph-loop execution

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After creating the PRD, start execution with:

    line 40

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

Ralph Init

Initialize a PRD (Product Requirements Document) for structured ralph-loop execution. Creates a structured requirements document that Ralph can use for goal-driven iteration.

Usage

/ralph-init "project or feature description"

Behavior

  1. Gather requirements via interactive interview or from the provided description
  2. Create PRD at .omx/plans/prd-{slug}.md with:
    • Problem statement
    • Goals and non-goals
    • Acceptance criteria (testable)
    • Technical constraints
    • Implementation phases
  3. Link to Ralph so that /ralph can use the PRD as its completion criteria
  4. Initialize/ensure canonical progress ledger at .omx/state/{scope}/ralph-progress.json (session scope if active session exists)

Canonical source contract

  • Canonical PRD source of truth is .omx/plans/prd-{slug}.md.
  • Ralph progress source of truth is .omx/state/{scope}/ralph-progress.json (session scope when available).
  • Legacy .omx/prd.json / .omx/progress.txt inputs are compatibility-only and migrate one-way into canonical artifacts.

Output

A structured PRD file saved to .omx/plans/ that serves as the definition of done for Ralph execution.

Next Steps

After creating the PRD, start execution with:

/ralph "implement the PRD"

Ralph will iterate until all acceptance criteria in the PRD are met and architect-verified.

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.