aid-methodology: Skill for Claude Code

Feature Definition from Approved Requirements

Agents Involved

aid-define is multi-agent — different states use different agents.

Decompose approved REQUIREMENTS.md into ### Feature NNN sections under § 11, then cross-reference the result against the Knowledge Base and codebase. Produces REQUIREMENTS.md §11 feature sections ready for /aid-specify.

Precondition: ## Interview State: Approved must be present in .aid/works/{work}/STATE.md. If requirements are not yet approved, run /aid-describe {work} first to gather and approve requirements.

Workspace structure:

.aid/
  knowledge/           <- shared KB (populated by /aid-discover)
  work-001-name/
    STATE.md           <- process (Interview State: Approved, Cross-Reference, Features State)
    REQUIREMENTS.md    <- approved requirements (/aid-describe) + §11 Features
                          (this skill) + each feature's Technical Specification
                          (/aid-specify). Features are sections; they have no
                          folders and no files of their own.

Accuracy note. interview.state/interview.grade/interview.sections[] are real keys in work-state-template.yml, and so is features[] -- this skill creates one entry there per ### Feature NNN section it appends to REQUIREMENTS.md § 11, and /aid-specify updates it as each feature advances. Features State was previously described here as "a DERIVED view with no key at all"; that was wrong, and it was not a harmless wrong -- the STATE.md -> STATE.yml converter believed it and refused to convert any work that had reached this phase. A per-feature "Cross-Reference" status and a Q&A-adjacent "Review History" list, as used below, do still carry no dedicated key -- they describe this skill's aspirational tracking design rather than a writable structure, and that remains an open schema gap. The Review History list now has a real target of its own, the review_history sequence, and Cross-phase Q&A entries have the qa sequence.