Capture spec change rationale as requirements
aida-doccommandsetup L1★3
joemooney/aida ↗What it does
Capture living documentation for recently-touched specs
Best for
Documenting the intent and design rationale of specs that were just modified or shipped
Inputs
- · Candidate spec from $ARGUMENTS or recent activity
- · User answers to seed questions (scenario, motivation, alternatives, example)
Outputs
- · Markdown documentation body
- · New DOC-N identifier confirmed
Requires
- · aida CLI (aida role show, aida doc show, aida doc add)
Preconditions
- · aida CLI installed and configured
- · Taproot project with aida initialized
Failure modes
- · aida CLI not in PATH
- · Spec not found in aida role
- · User cancels during question phase
Trust signals
- · References existing aida doc show output
- · Follows .claude/skills/aida-doc.md workflow
- · Asks max three seed questions (not exhaustive, user-driven)