Menu
Define testable, scoped requirements
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.
Based on SOC occupation classification
Review dimension for naming, idiom, comment debt, and AI tells against the codified per-language and prose standards. Invoked by reviewer agents over one module shard.
Recipe for writing C in the runtime, module placement and the ownership and control-flow discipline. Invoked by writer agents when a C unit is dispatched.
Recipe for writing Clojure, Functional Core / Imperative Shell at the function level (namespaces by domain), native wrappers, and the boundary discipline. Invoked when writing Clojure for the project.
Recipe for writing Elixir, pure functions in modules as the core and GenServer plus OTP as the shell, supervision trees, and NIF discipline for the C and Zig edge. Invoked when writing Elixir for the project.
Recipe for any English the agent produces in this project, commits, comments, docstrings, ADRs, design docs, skill bodies, changelog, error messages, project guides. Optimizes for terse, humanized prose with no em dashes and no AI tells. Invoke for any prose-writing activity.
Recipe for writing Zig, native bodies and edge wrappers, the allocator and lifetime discipline, and the hot-path rules. Invoked when writing or editing any Zig source.
| name | define-requirements |
| description | Define testable, scoped requirements |
| user-invocable | false |
Define WHAT must be built as testable, scoped requirements. No tech stack, architecture, timelines, or estimates.
project-meta.md, problem-description.md, and open-questions.md.
If a prerequisite is missing, return blocked: <which artifact>.[Blocking] items affecting product-requirements.md and
resolve them first.open-questions.md as - [ ] [Affects: product-requirements.md] <question> (Answer: TBD).~/.agentic-sdk/<project>/artifacts/planning/product-requirements.md with: Metadata,
Problem Statement, Goals, Non-Goals, Users, Scope, Functional Requirements
(each with priority and acceptance criteria), Non-Functional Requirements,
Workflows, Success Criteria, Assumptions. Keep open questions out of the
PRD; they live in open-questions.md.Owns the testable requirements. review-risks owns surfacing risk and assumptions; design-technical owns HOW. Reached by plan-system.
One line: the artifact written and a terse status, or blocked: <reason>.