# Prd Light

> Trigger: PRD light, quick PRD, lightweight PRD, MVP requirements. Create lightweight PRDs for small features, internal tools, and early ideas.

- Skill: `andresnator/prd-light` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add andresnator/prd-light`
- Raw SKILL.md: https://api.skillmd.com/api/skills/andresnator/prd-light/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: andresnator (https://skillmd.com/u/andresnator)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/andresnator/prd-light

---


# PRD Light

## Activation Contract

Use this skill to create a useful, lightweight PRD quickly. It is for MVPs, internal tools, small-to-medium features, and early ideas where the team needs shared direction without formal review ceremony.

Always read `assets/prd-light-template.md` at the start of the session and use it as the final document skeleton.

## Hard Rules

- Keep the conversation brief and practical.
- Work one phase at a time.
- Ask at most one follow-up per phase unless missing information fully blocks the document.
- Ask open-ended questions directly in normal chat; use the `question` tool only for a closed confirmation or enumerated choice.
- Add `Recommendation: ...` only when it helps the user respond. Do not add question headings, numbering, rationale blocks, or interview-length estimates.
- Accept plain-language acceptance criteria; Given/When/Then is optional.
- Skip non-relevant details easily; use `N/A` without heavy justification.
- Produce a useful draft fast instead of chasing perfect completeness.
- Do not invent unknowns; use open questions or assumptions when needed.
- Use the reference template for the final artifact.
- Ask where to save the PRD after presenting the final draft; suggest `PRD-Light-{product-name}-v{version}.md` if the user wants a default.

## Conversation Format

Use this minimal shape for open interview questions:

```markdown
[Direct question]

Recommendation: [short recommended/default answer when useful]
```

Omit the recommendation line when it adds no value.

## Decision Gates

| Situation | Action |
| --- | --- |
| Intent is ambiguous | Ask one plain-language question: what are we planning and who needs to use the document? |
| Discussion is becoming too ceremonial | Collapse detail into bullets, capture open questions, and move forward. |
| Scope is missing | Ask what is in, what is out, and what the first useful version includes. |
| Success is missing | Ask how the team will know the work was worth shipping. |
| Requirements are missing | Ask for the 3-7 behaviors or outcomes the product must support. |
| Delivery is missing | Ask what should ship first and any known date or dependency. |
| Missing detail does not block alignment | Record it as an open question and continue. |

## Execution Steps

1. Read `assets/prd-light-template.md`.
2. Phase 1, Context and Goals: capture problem, goal, scope, non-goals, and success signals.
3. Phase 2, Users and Scenarios: capture target users and the core user/system scenarios.
4. Phase 3, Requirements: capture concise requirements, priority, and plain-language acceptance criteria.
5. Phase 4, Approach and Constraints: capture the proposed approach, key constraints, dependencies, and relevant technical notes.
6. Phase 5, Risks, Open Questions, and Delivery: capture risks, assumptions, open questions, MVP/first release, and next milestones.
7. Generate the final PRD Light from the template, replacing placeholders with collected content and marking gaps clearly.
8. Present the final draft for review and ask where to save it.

## Validation Rules

- The problem and intended outcome are understandable in plain language.
- Scope includes the first useful version and at least one boundary.
- Success criteria are observable, even if lightweight.
- Requirements are concrete enough for a builder to start.
- Must-have requirements have acceptance criteria.
- Each must-have requirement connects to a goal or scenario.
- Constraints and dependencies mention only what changes delivery or design.
- Risks and open questions are visible.
- The delivery section identifies the MVP or first useful release.

## Output Contract

Return a concise PRD Light document in Markdown using `assets/prd-light-template.md`.

After the draft, include a brief final review request covering:

- Anything still marked `TBD` or open.
- Whether the MVP/first release feels correct.
- Suggested save path or a question asking where to save the file.

## References

- `assets/prd-light-template.md` — lightweight PRD template.