Borrowing it
Nothing to install: this file belongs to luiscielak/ai-product-design-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luiscielak/ai-product-design-rules/main/.cursor/skills/ai-product-design-prd/SKILL.mdgit clone --depth 1 https://github.com/luiscielak/ai-product-design-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-prd)<a href="https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-prd"><img src="https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-prd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-prd"><img src="https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.00709 |
| Opus 5.5 | $0.00020 | $0.00284 |
| Sonnet 5.5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
ai-product-design-prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD (Product Owner)
Produce a concise, actionable PRD aligned to measurable success metrics.
Pipeline
Stage in the ai-product-design chain:
scaffold → /prd → /lofi → /midfi → /hifi → /ui-proto.
- Previous: scaffold (ai-product-design-new-project)
- Next:
/lofi(ai-product-design-lofi)
To run the whole chain in one pass, use the ai-product-design-workflow
orchestrator.
Inputs
Required: product_name, target_users, key_problem, business_goals, success_metrics, primary_flows (list).
Also: constraints, assumptions, risks, stakeholders, timeline.
Artifact root
All deliverables for this product go under a single artifact_root:
- Definition:
artifact_rootis the directory that contains this product’sPRD.mdand/orDESIGN-BRIEF.md(same folder is ideal). If files are split, prefer the folder the user attached or the one containingPRD.md. - Resolve in order: (a) Parent directory of an attached or @-referenced
PRD.md/DESIGN-BRIEF.md; (b) explicit path the user gives for the product docs folder; (c) greenfield only (/new-projector PRD with no path):projects/{project_name}/docs/. - Do not default to repo-global
docs/wireframes/,docs/ui-design/, or rootdocs/PRD.mdwhenartifact_rootis known.
Output
File: {artifact_root}/PRD.md — for greenfield with no path yet, use projects/{project_name}/docs/PRD.md as artifact_root.
PRD Content Structure
- Overview — product_name, elevator_pitch, problem_statement
- Goals and Non-Goals
- Target Users and Personas
- User Stories (INVEST) and Primary Flows
- Scope — MVP vs Post-MVP
- Functional Requirements — FR-001, FR-002… (each maps to a user story and metric)
- Non-Functional Requirements — NFR-001…
- Acceptance Criteria — Gherkin-style where useful
- Success Metrics — north star + leading indicators (target, timeframe, measurement method each)
- Dependencies and Constraints
- Assumptions and Open Questions
- Risks and Mitigations
- Release Plan and Milestones
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 63 lines · 50 tokens per session scan A dad3d15d1ab3
ai-product-design-prd is a skill published in the GitHub repository luiscielak/ai-product-design-rules (4 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 709 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-28.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…