agentleFS
Sign inStart free
felipeam86felipeam86/pipe-skills/skills/prd/SKILL.md

prd

Skill18 starsChanged 11 days agoMITView on GitHub

Create an outcome, or an issue that is the specification for its own implementation, or update one after the plan changes, in Linear or GitHub Issues. For a project whose CLAUDE.md names where it tracks work. Use when the user says "create an issue for this effort", "push this as an issue", "update issue ABC-123", "update issue #42", "track this in an issue", or runs /pipe-skills:prd in such a project.

127 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use context-optimize, usecase and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ibahgatSkill

    context-optimize

    Improve context efficiency and cache stability for long or complex sessions.

    Also in 3 projects that use this

  • gabriellstSkill

    usecase

    Create an application use case. Use when implementing business operations like CreateOrder, ProcessPayment, CancelBooking. Use this skill for any command/mutation that orchestrates domain logic, whether simple CRUD or complex multi-step transactions with sagas. Dispatch hub — routes to typescript/go variants by file extension.

    Also in 3 projects that use this

  • jidechaoSkill

    modern-go

    Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code", "gofix", or wants to upgrade Go idioms.

    Also in 3 projects that use this

  • ulises-jeremiasSkill

    trd

    WHAT — Draft and review a Technical Requirements Document (TRD) using the template, typically

    Also in 3 projects that use this

  • jidechaoSkill

    loop-it

    Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.

    Also in 3 projects that use this

  • snarktankSkill

    ralph

    Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.

    Also in 16 projects that use this

  • +2 more from jidechao

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 104 edited versions we read keep these.

  • 0

    Distinctive

    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:

    When the plan changes, rewrite the description to the current proposal only, with pipe-skills:final-state, and add a comment with the …

    line 35
  2. Very specific:

    Write each paragraph or bullet as one line, with real newlines, not \n escapes.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 104 edited versions of this file we could read. “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

Issue as PRD

An issue is the specification for its implementation: the design and the plan live in the issue, not in a document in the repository.

The project CLAUDE.md names where it tracks work. Read the tracker file for it, ${CLAUDE_PLUGIN_ROOT}/trackers/linear.md or ${CLAUDE_PLUGIN_ROOT}/trackers/github.md, and run each operation below as that file says. If the project CLAUDE.md names no tracker, stop and offer /pipe-skills:setup.

An outcome holds issues, and the tracker file says what an outcome is. Order issues with "blocked by" relations. Link issues as children of a parent issue only when the group is itself a piece of work with its own success criteria, with the parent link of the tracker file.

Draft first

Show the draft before you file. Read the outcomes with their descriptions, put each issue in the outcome whose goal it serves, and name that outcome in the draft with a one-line reason. Propose a new outcome only for a goal that no outcome covers, with its own success criteria and more than one issue. Ask the user when two outcomes fit, when none fits, or when the work covers more than one. List each open decision with the options and your recommendation, and ask whether the scope is complete. File only after the user's go.

Outcome

Sections: Description (one line), Goal, Business impact, Success criteria, Risks. Set the target date. Its issues are its plan.

Issue

The case, written when the issue is planned: Description (one line), Goal, Business impact, Success criteria (how you prove it), Risks.

The issue says what the work must achieve and what it is worth, not how to build it. The Business impact gives the weight of the work: what it costs today, how often, and for whom, because implement sizes the change and review sizes its bar from it. The Success criteria say what done looks like. Name a method, a plan, or a list of edge cases only when the user decided it, and mark it as decided, because each prescribed guard is more for the implementer to build and for the reviewer to attack.

The design, added when the work starts: State (what exists today), Options (when there is more than one path), Plan (only the steps the user decided, in order), Context (the decisions and what else a reader needs).

Drop a section that holds nothing. File the issue in its outcome, assigned to the user, in state Todo, with its priority and its "blocked by" relations, so that pipe-skills:autonomous-loop takes the issues in the correct order. Give the identifier and the URL, and offer to run pipe-skills:implement.

Update

When the plan changes, rewrite the description to the current proposal only, with pipe-skills:final-state, and add a comment with the change and its reason. When the issue serves another outcome, move it there after the user's go, and say why in the same comment.

Close

/pipe-skills:ship closes the issue after the merge. To close it by hand, first ask the user: "do you think we are ready to close this issue?"

Write each paragraph or bullet as one line, with real newlines, not \n escapes.

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