agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/create-prd/SKILL.md

create-prd

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to create, draft, write, update, structure, or turn an idea into a Product Requirements Document, PRD, product requirements, feature requirements, feature spec, product spec, MVP scope, release requirements, or build requirements for a product, feature, module, service, workflow, or user experience. Use when the output needs problem, background, objective, target segment, customer value, requirements, UX notes, feature scope, assumptions, success metrics, release plan, MVP versus later scope, or development guidance. Use for prompts like write a PRD, create a feature spec, document product requirements, turn this idea into requirements, define MVP requirements, what should v1 include, or prepare requirements for engineers and designers. Do not use for broad product direction without requirements, serious approval memos, PR/FAQ artifacts, delivery sequencing, customer-facing support docs, customer journey maps, pure critique, or formal pass/fail validation. If the primary task is product strategy or product direction, use product-strategy. If the primary task is a serious written decision memo, PR/FAQ, or board-grade approval artifact, use working-backwards. If the primary task is roadmap, dependency tree, work packages, issue tree, or execution sequencing, use wbs-artifact-planner. If the primary task is customer-facing help, API, setup, or troubleshooting documentation, use support-docs. If the primary task is end-to-end customer journey, onboarding friction, touchpoints, or pain points, use customer-journey-map. If the primary task is validating whether an existing PRD is ready, use artifact-validation-workflow. If the primary task is skeptical critique of an existing PRD's logic, evidence, or assumptions, use deep-critic.

44 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use prioritize-features, brainstorm-okrs and 9 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.
  • skytiger6724Skill

    prioritize-features

    Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.

    Also in 4 projects that use this

  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 4 projects that use this

  • miovragSkill

    strategy-red-team

    Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

    Also in 3 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 4 projects that use this

  • About-IntelligenceSkill

    beachhead-segment

    Identify the first beachhead market segment for a product launch.

    Also in 4 projects that use this

  • About-IntelligenceSkill

    value-proposition

    Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives.

    Also in 4 projects that use this

  • +5 more from skytiger6724

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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