skills.rest
sizukutamago
sizukutamagoCOMMUNITY
Explore all skills by this author →
GitHub

requirements

Structure ambiguous development tasks into formal requirements documents with FR and AC sections.

Updated Mar 29, 2026
Search Tags:#documentation#requirements#exploration#spec#decision-tracking#ac#fr
One-click install
npx skills add https://github.com/sizukutamago/claude-code-harness --skill requirements-sizukutamago
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/sizukutamago/claude-code-harness/tree/main/.claude/skills/requirements
Command: npx skills add https://github.com/sizukutamago/claude-code-harness --skill requirements-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many implementation tasks begin with ambiguous or incomplete instructions that lead to incorrect or drifting implementations. This Skill structures the conversation, investigation, and decisions so that human and AI collaborators share an approved, machine- and human-readable requirements artifact before development begins.

Core Features & Use Cases

  • Structured investigation: Delegates codebase and document research to an Explore subagent while the main session focuses on shaping the problem with the human partner.
  • Differential, low-friction hearing: Generates targeted, choice-oriented questions to resolve only the unknowns and records answers in a context.md file.
  • Template-driven outputs: Produces a requirements/REQ-*/requirements.md containing FR/AC/NFR and scope, a context.md with background and Q&A, and an optional decisions.md for scope decisions and alternatives.
  • Use case: Prepare an approved requirements package for a new feature, a multi-file bugfix, or a specification change so implementers and verifiers have clear acceptance criteria.

Quick Start

Ask the assistant to run the requirements skill with a short task description so it can investigate, ask clarifying questions, and produce a requirements/REQ-001-<slug>/requirements.md plus context.md for approval.

Frequently Asked Questions about requirements

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

FAQPage Schema
How do I turn ambiguous development tasks into clear requirements?▼

Structured requirements documents include Functional Requirements (FR), Acceptance Criteria (AC), Non-Functional Requirements (NFR), and scope definitions, which are generated inside a requirements.md file to guide implementers and verifiers.

How do I write formal feature specifications from vague instructions?▼

This Skill applies to new feature development, multi-file bug fixes, and specification changes where investigation, scoped FR/AC definitions, and human approval are needed before implementation begins.

What is the best way to track decisions and context during requirements exploration?▼

It generates targeted, choice-oriented questions to resolve only the unknowns and records the answers in a context.md file, keeping the hearing process differential and low-friction.

Does this requirements generation process work for multi-file bug fixes?▼

It produces a requirements/REQ-<id>/requirements.md with FR and AC sections, ensuring implementers and verifiers have clear acceptance criteria for complex bug fixes.

When do I need a formal requirements document for software development?▼

This Skill structures the conversation, investigation, and decisions so that human and AI collaborators share an approved, machine- and human-readable requirements artifact before development begins.

Can I use an Explore subagent to research the codebase while defining requirements?▼

The Skill delegates codebase and document research to an Explore subagent while generating targeted questions to resolve unknowns and recording answers in a context.md file.

Related Skills

Explore More Software Engineering Skills→
oryanmosheoryanmoshe
2

exploring-in-parallel

Launch parallel subagents to explore codebases and research questions.

Community
Intermediate
sunrain520sunrain520
72

spec-first:spec

Define functional requirements and acceptance criteria through a structured multi-phase workflow.

Community
Advanced
scooter-lacroixscooter-lacroix
8

research

Document existing codebase structure and component interactions through parallel agentic research.

Community
Advanced
SensLiaoSensLiao

gsd-ns-ideate

Explore ideas, sketch designs, run technical spikes, and write specifications.

Community
Intermediate