requirements-clarification

Convert raw implementation requests into atomic requirement records with explicit statuses.

Updated Mar 29, 2026

Search Tags:#planning #requirements #clarification #handoff #artifact #atomic-records

Ready to run

npx skills add https://github.com/ZenkakuHiragana/my-chezmoi-config --skill requirements-clarification-zenkakuhiragana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-clarification
Source: https://github.com/ZenkakuHiragana/my-chezmoi-config/tree/main/dot_config/opencode/skills/requirements-clarification
Command: npx skills add https://github.com/ZenkakuHiragana/my-chezmoi-config --skill requirements-clarification-zenkakuhiragana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a raw, implementation-shaped request into an execution-ready requirements artifact by decomposing it into atomic requirements, normalizing each into fixed records, and assigning explicit attribute statuses (user_provided, repo_derivable, public_fact, or unknown).

Core Features & Use Cases

Splits a user instruction into atomic requirements.
Normalizes each atomic requirement into fixed records with explicit statuses.
Outputs a written requirements artifact to .opencode/work/req-requirements-clarification.md and provides a single handoff recommendation.
Helps reduce ambiguity and guide downstream planning and execution.

Quick Start

Convert a vague implementation request into atomic requirements.

Frequently Asked Questions about requirements-clarification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break down a vague implementation request into atomic requirements?▼

To break down a vague implementation request into atomic requirements, decompose the raw instruction into individual needs and normalize each into fixed records with explicit attribute statuses like user_provided, repo_derivable, public_fact, or unknown.

What is the best way to normalize ambiguous requirements for downstream execution?▼

Normalizing ambiguous requirements involves splitting a raw instruction into atomic needs and assigning each an explicit attribute status, producing an execution-ready artifact that reduces ambiguity and guides downstream planning.

How do I assign attribute statuses to incomplete software requirements?▼

Assigning attribute statuses to incomplete requirements involves categorizing each atomic need as user_provided, repo_derivable, public_fact, or unknown, ensuring explicit tracking of missing information before execution begins.

Where are clarified requirements artifacts stored for project handoff?▼

Clarified requirements artifacts are written to .opencode/work/req-requirements-clarification.md, providing a normalized record of atomic needs alongside a single handoff recommendation for downstream execution.

When should I use a requirements clarification process for implementation tasks?▼

Use a requirements clarification process for ordinary implementation-shaped tasks where the initial instruction is incomplete, ambiguous, or contains multiple atomic needs that require decomposition before execution.

Can I process multiple atomic needs within a single project request?▼

Processing multiple atomic needs within a single request involves splitting the raw instruction into individual atomic requirements, normalizing each into fixed records, and assigning explicit attribute statuses to prepare them for execution.