agentleFS
ibahgatibahgat/oh-my-iflow/skills/prd/SKILL.md

prd

Skill2 starsChanged 8 months agoMITView on GitHub

Convert a request into PRD-quality scope, measurable acceptance criteria, and delivery constraints.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 96 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Use this skill to lock scope before implementation starts.

    line 8
  2. Distinctive:

    Write a concise problem statement.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 96 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

Purpose

Use this skill to lock scope before implementation starts.

Trigger

  • Requirements are ambiguous or too broad
  • Team needs measurable done criteria
  • Scope creep risk is high

Workflow

  1. Write a concise problem statement.
  2. Define in-scope and explicit non-goals.
  3. Define acceptance criteria with evidence requirements.
  4. Capture constraints and dependencies.
  5. Produce handoff notes for execution and verification.

Output Template

## Problem Statement
- ...

## Scope / Non-goals
- ...

## Acceptance Criteria
| Criterion | Evidence Needed | Owner |
| --- | --- | --- |

## Constraints
- ...

## Handoff
- ...

Download now (ZIP)

  • Other versions118 projects use a version of this.

    Word for word · 0

    None found.

    Wrote their own version · 116

    1. github/awesome-copilot★ 41ksame name
    2. snarktank/ralph★ 22ksame name
    3. SethGammon/Citadel★ 927same name
    4. smallnest/autoresearch★ 571same name
    5. snarktank/compound-product★ 542same name
    6. CatCatUncle/openworkbuddy★ 348same name
    7. smallnest/goal-workflow★ 283same name
    8. OffchainLabs/arbitrum-docs★ 252same name
    9. golbin/agent-skills★ 214same name
    10. julianromli/ai-skills★ 207same name

    106 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use modern-go, to-design and 8 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.
    • 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

    • jidechaoSkill

      to-design

      Generate a design document (design proposal) from a PRD, in the style of Go's official design proposals — Abstract / Background / Design / Rationale / Compatibility / Implementation, heavy on the 'why' and tradeoffs. Triggers on: to-design, prd-to-design, prd转设计文档, 生成设计文档, 写设计文档, design doc, design proposal, 设计提案, 技术设计文档.

      Also in 3 projects that use this

    • meganzSkill

      usecase

      Create, update, and refactor Android Use Cases using Test-Driven Development (TDD). Enforces writing test cases before production code, follows project use case conventions (@Inject constructor, operator fun invoke, single responsibility), and supports three modes: create, update, and refactor.

      Also in 3 projects that use this

    • JokerRunSkill

      compound-engineering

      Compound Engineering workflow for AI-assisted development. Use when planning features, executing work, reviewing code, or codifying learnings. Follows the Plan → Work → Review → Compound loop where each unit of engineering makes subsequent work easier. Triggers on: plan this feature, implement this, review this code, compound learnings, create implementation plan, systematic development.

      Also in 3 projects that use this

    • deedeeharrisSkill

      prd-to-spec

      Convert an approved PRD into a phase-gated implementation SPEC. User-facing entry point that dispatches to the prd-to-spec babysitter process via /babysitter:call (interactive) or /babysitter:yolo (auto). Stack-agnostic.

      Also in 3 projects that use this

    • dirkkok101Skill

      review-prd

      Use before /technical-design, after /prd, when user says "review prd", "check requirements", or when PRD quality is uncertain.

      Also in 3 projects that use this

    • +2 more from jidechao
  • In this repository24 other files it gives its agents.

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.