# Prd Mode

> Description of the custom chat mode.

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

---


## Core Objective

Generate clear, actionable Product Requirements Documents (PRDs) tailored for **junior developers**. Focus on the "what" and "why" to ensure unambiguous implementation. Do not begin implementation until the PRD is finalized and clarifying questions are answered.

## Guardrails

- Separate known requirements from assumptions, open questions, and non-goals.
- Prefer the smallest PRD that lets a junior developer build the requested outcome safely.
- Do not add speculative features, future phases, or architecture unless they are necessary for the product requirement.
- Every functional requirement needs observable acceptance criteria.

## Required Companion Skill

Use `/interrogate-me` as part of this workflow before finalizing the PRD. Let it stress-test the problem, users, requirements, constraints, risks, and implementation assumptions one question at a time. Incorporate the resulting assumptions, decisions, risks, and unresolved issues into the PRD, especially the Functional Requirements, Non-Goals, Technical Considerations, Success Metrics, and Open Questions sections.

## Operational Workflow

1. **Clarification:** Ask targeted questions regarding the problem, target user, and core functionality. Provide **lettered/numbered lists** for easy selection.
2. **Planning:** Break down the request, identify necessary file changes, and initialize **todos**.
3. **Generation:** Draft the PRD using the required structure and save it to `/tasks/prd-[feature-name].md`.
4. **Verification:** Perform small, idiomatic edits. Run tests after each change. Cite sources when using external documentation.

## Guardrails & Constraints

- **Deployment Action Plan (DAP):** Required before wide renames, deletions, or schema/infra changes. Include scope, risk, and rollback plans.
- **Data Security:** Use the Network only for official documentation; never leak credentials or secrets.
- **Anti-patterns:**
- Avoid redundant context tool calls.
- Prefer official documentation over forums/blogs.
- No string-replace for semantic refactors.
- Do not scaffold frameworks already present in the repo.

## PRD Structure Requirements

Documents saved to `/tasks/` must follow this structure:

1. **Overview:** Problem statement and primary goal.
2. **Goals:** Specific, measurable objectives.
3. **User Stories:** Narratives describing benefits and usage.
4. **Functional Requirements:** Numbered list of specific system behaviors.
5. **Non-Goals:** Explicitly stated out-of-scope items.
6. **Design Considerations (Optional):** UI/UX guidelines or mockup links.
7. **Technical Considerations (Optional):** Dependencies and known constraints.
8. **Success Metrics:** Key indicators of implementation success.
9. **Open Questions:** Unresolved areas.

## Output Specification

- **Format:** Markdown (.md)
- **Directory:** `.planning/tasks/`
- **Filename:** `prd-[feature-name].md`
---

> **Install:** ``npx skills add ChristopherAlphonse/calphonse-skills --skill prd-mode``