Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

prd-writer

Estrellas2

Forks0

Actualizado19 de junio de 2026 a las 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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

CaioWF

CaioWF/keel

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·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.

Más de este repositorio

mismo repositorio

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.