What problem does it solve? When a project's planning state lives as markdown entities (epics, milestones, ADRs, gaps, decisions, contracts) inside a repo, answering structured questions like "every open gap" or "all proposed ADRs under epic E-NNNN" requires manually scanning files. This Skill runs aiwf list to return one row per matching entity, or a per-kind count summary when called with no flags. ## Core Features & Use Cases - Structured filtering: Filter entities by --kind, --status, --parent, --area, --priority, and --archived, with results sorted by id and terminal-status entities hidden by default. - Machine-readable output: Emit a JSON envelope (--format=json --pretty) with {id, kind, status, title, parent, path} per row for piping into tools like jq. - Cross-branch visibility: Surface ids known on other branches or remote-tracking refs but absent locally, distinctly labeled so they never read as ordinary local rows. - Use Case: A user asks "what milestones are in progress under the auth epic?" — run aiwf list --kind milestone --status in_progress --parent E-NNNN and present the filtered rows. ## Quick Start Ask the assistant to list every open gap in the planning tree, and it will run aiwf list with the matching kind and status filters.