Menu
Turn current context into a PRD and publish it to issue tracker.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | to-prd |
| description | Turn current context into a PRD and publish it to issue tracker. |
Synthesize current context into PRD. Do not interview unless blocked.
Issue tracker + triage labels should exist. If missing, ask which tracker and labels to use.
ready-for-agent.## Problem Statement
User-facing problem.
## Solution
User-facing solution.
## User Stories
1. As an <actor>, I want <feature>, so that <benefit>.
## Implementation Decisions
Modules, interfaces, clarifications, architecture, schema/API contracts. No stale file paths. Prototype snippets allowed only if decision-rich.
## Testing Decisions
Good-test shape, modules tested, similar prior tests.
## Out of Scope
What not doing.
## Further Notes
Extra context.
Generate Codex hooks.json and AGENTS.md from Claude Code hooks. Maps supported hooks directly, including Edit|Write apply_patch aliases, and keeps Stop batch checks only as fallback. Use when setting up Codex compatibility or dual-agent support.
Question changed code as liability and remove unjustified surface area. Use before commit, push, PR, merge, or when a change feels overbuilt or low-value.
Reviews diffs for over-engineering only. Use when reviewing, desloping, or asking what to delete, inline, shrink, or replace with stdlib/native code.
Resilience Review checks resilience. Use when edge cases, errors, fallback, async/data, state, or polish matter.
Reviews a diff since a fixed point across Standards, Spec, and risk gates. Use when reviewing a branch, PR, WIP, or "review since X".
parallel executor. Use /swarm.