Menu
Extract requirements from a request: behavior, AC, constraints; for bugs - repro
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
Mandatory baseline rules for any agent. Must be loaded before any work
Frontend design system practices: tokens, typography, color, layout, and component consistency.
Frontend UI/UX practices: flows, interaction states, accessibility-first UX, forms, and perceived performance.
Clean code execution rules for coding agents with verifiable quality gates.
Debugging requirements protocol from reproducible issue to verified fix and regression protection.
Requirement quality rules for coding tasks with traceable MUST/SHOULD and verifiable acceptance criteria.
| name | planning-requirements-extraction |
| description | Extract requirements from a request: behavior, AC, constraints; for bugs - repro |
<output_format>
<quality_rules> AC are specific, verifiable, and contain no implementation details Constraints/dependencies are not lost (if they affect the plan) For bugs, facts are explicitly separated from hypotheses </quality_rules>
<do_not> Do not turn requirements into a list of technical tasks Do not invent AC without evidence - if data is missing, it is an open question </do_not>
