requirement

Converts raw user requirements into spec documents, backlog entries, and logs.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Samind-Samind/projexa --skill requirement-samind-samind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirement
Source: https://github.com/Samind-Samind/projexa/tree/main/.claude/skills/requirement
Command: npx skills add https://github.com/Samind-Samind/projexa --skill requirement-samind-samind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw feature requests and requirements often get lost or documented inconsistently. This Skill turns informal requirement conversations into structured specification documents, keeps the project backlog synchronized, and maintains an audit log, all with human confirmation before any file is written. ## Core Features & Use Cases - Requirement Intake and Clarification: Collects free-form requirements in Thai or English, then asks structured follow-up questions (always with at least three options) whenever scope, priority, or acceptance criteria are ambiguous. - Duplicate and Overlap Detection: Scans existing specs in docs/01-requirements/01-spec/ and the backlog to decide whether to create a new document or extend an existing one. - Human-in-the-Loop Writing: Summarizes the planned changes for user confirmation, then delegates file creation to a one-shot requirement-writer sub agent that writes the spec, updates backlog.md, and appends to the dated log. - Use Case: A product owner describes a new screen-tracking feature in chat; the Skill checks for overlapping specs, clarifies acceptance criteria, gets confirmation, and produces a dated spec file plus updated backlog and log entries. ## Quick Start Tell the assistant to use the requirement skill to turn this feature idea into a spec document and update the backlog.

Frequently Asked Questions about requirement

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

FAQPage Schema
How do I document a new software requirement from a chat conversation?▼

Describe the requirement in free-form text, and the Skill collects details through clarifying questions, checks existing specs for overlap, summarizes the plan for your confirmation, then writes the spec, backlog entry, and log via a sub agent.

How does the requirement skill handle duplicate or overlapping requirements?▼

It scans docs/01-requirements/01-spec/ and backlog.md for related documents, then asks you whether to create a new spec, extend the existing one, or link the two, always offering at least three options.

Can I write requirements in Thai or English?▼

Yes, the Skill accepts raw requirements in either Thai or English as free-form text. It does not force any specific format during the intake step and clarifies ambiguities through follow-up questions.

Does the requirement skill write files without user confirmation?▼

No, it follows a strict human-in-the-loop principle. It summarizes the planned spec, backlog, and log changes and waits for explicit confirmation before delegating file writes to the requirement-writer sub agent.

What files does the requirement-writer sub agent create or update?▼

It creates or edits a spec file in docs/01-requirements/01-spec/, updates docs/01-requirements/backlog.md, and appends an entry to the dated log at docs/05-log/(YYYYMMDD)-log.md, using the current date supplied in the prompt.