Menu
Clarify the user problem, constraints, and success criteria
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 | describe-problem |
| description | Clarify the user problem, constraints, and success criteria |
| user-invocable | false |
Clarify the real user problem, constraints, and success criteria in user and business terms. Define WHAT, not HOW.
~/.agentic-sdk/<project>/artifacts/project/project-meta.md and
~/.agentic-sdk/<project>/artifacts/decisions/open-questions.md. If either is missing,
return blocked: bootstrap the planning artifacts first.open-questions.md under Open as
- [ ] [Affects: problem-description.md] <question> (Answer: TBD); mark
[Blocking] only if you cannot proceed.~/.agentic-sdk/<project>/artifacts/planning/problem-description.md with these
sections: Metadata, Summary, Problem, Desired Outcomes, Stakeholders,
Current Workflows, In Scope, Out of Scope, Constraints, Risks, Unknowns,
Simplification Opportunities, References.Owns the problem in user and business terms. define-requirements owns the testable requirements; design-technical owns the architecture. Reached by plan-system.
One line: the artifact written and a terse status, or blocked: <reason>.