Run any Skill in Manus with one click

prd-writer

Stars2

Forks0

UpdatedJune 19, 2026 at 00:52

Use after brainstorming settles on a feature idea to write the Product Requirements Document for a new feature into specs/<feature>/prd.md from the PRD template, creating the feature's spec folder and marking it active.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

CaioWF

CaioWF/keel

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	prd-writer
description	Use after brainstorming settles on a feature idea to write the Product Requirements Document for a new feature into specs/<feature>/prd.md from the PRD template, creating the feature's spec folder and marking it active.

prd-writer

When: a feature idea has been shaped (e.g. via brainstorming) and is ready to be written down before any spec/code work starts.

Template: .specify/templates/prd-template.md.

Output: specs/<feature>/prd.md, where <feature> is NNN-kebab-case-name.

Steps:

Determine the next ordinal NNN: list existing specs/* directories, take the highest leading number, zero-pad the increment to 3 digits (first feature is 001).
Choose a short kebab-case name for the feature; create specs/NNN-name/.
Copy .specify/templates/prd-template.md to specs/NNN-name/prd.md.
Fill each section that exists in the template:
- Problema — the problem/opportunity and its impact.
- Hipótese — the solution hypothesis and why it should work.
- Usuário/Contexto — target user, usage scenarios, constraints.
- Métrica de Sucesso — measurable KPI/OKR for success.
- Fora de Escopo — what this phase explicitly excludes.
Write NNN-name (single line, no trailing content) to .specify/state so it becomes the active feature for subsequent skills.

Next: spec-writer.

More from this repository

same repository

okf-enrich

CaioWF/keel

Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.

2026-07-112

finishing-a-development-branch

CaioWF/keel

Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.

2026-07-102

subagent-driven-development

CaioWF/keel

Use when executing implementation plans with independent tasks in the current session

2026-07-102

implement-and-evaluate

CaioWF/keel

Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.

2026-07-102

tasks-writer

CaioWF/keel

Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.

2026-07-102

observability-and-instrumentation

CaioWF/keel

Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.

2026-07-082

name	prd-writer
description	Use after brainstorming settles on a feature idea to write the Product Requirements Document for a new feature into specs/<feature>/prd.md from the PRD template, creating the feature's spec folder and marking it active.

prd-writer

When: a feature idea has been shaped (e.g. via brainstorming) and is ready to be written down before any spec/code work starts.

Template: .specify/templates/prd-template.md.

Output: specs/<feature>/prd.md, where <feature> is NNN-kebab-case-name.

Steps:

Determine the next ordinal NNN: list existing specs/* directories, take the highest leading number, zero-pad the increment to 3 digits (first feature is 001).
Choose a short kebab-case name for the feature; create specs/NNN-name/.
Copy .specify/templates/prd-template.md to specs/NNN-name/prd.md.
Fill each section that exists in the template:
- Problema — the problem/opportunity and its impact.
- Hipótese — the solution hypothesis and why it should work.
- Usuário/Contexto — target user, usage scenarios, constraints.
- Métrica de Sucesso — measurable KPI/OKR for success.
- Fora de Escopo — what this phase explicitly excludes.
Write NNN-name (single line, no trailing content) to .specify/state so it becomes the active feature for subsequent skills.

Next: spec-writer.