What problem does it solve? When humans and AI assistants plan a project across many sessions, new planning records (epics, milestones, ADRs, gaps, decisions, contracts) get created inconsistently — hand-written files with colliding ids, missing frontmatter, and untraceable commits. This Skill runs the aiwf add verb so id allocation, frontmatter shape, body scaffolding, and the trailered git commit all happen mechanically. ## Core Features & Use Cases - Entity creation for six kinds: Allocate and create epics, milestones, ADRs, gaps, decisions, and contracts with kind-specific required flags and stable ids (E-NNNN, M-NNNN, ADR-NNNN, G-NNNN, D-NNNN, C-NNNN). - Acceptance criteria under milestones: Add one or many ACs atomically with repeated --title flags and positional --body-file pairing, seeded at the pre-cycle empty TDD phase. - Body content in the create commit: Pass --body or --body-file (including stdin) so real prose lands in the same atomic commit, avoiding untrailered follow-up edits; born-complete kinds (gap, decision, ADR, contract) refuse empty load-bearing sections unless --force --reason is given. - Milestone dependency edges: Declare depends_on DAG edges at allocation time or post-allocation via aiwf milestone depends-on, with replace-not-append semantics. - Use Case: While reviewing a design doc with your AI assistant, you discover a defect. The assistant drafts the gap body and runs aiwf add gap --title "Retry loop spins forever" --body-file gap-body.md, producing a validated entity file and one trailered commit. ## Quick Start Ask the assistant to add a new aiwf entity, for example: create a gap titled "Retry loop spins forever" with the body describing what is missing and why it matters.