| name | aip-tracker |
| description | Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status. |
| license | Apache-2.0 |
AIP Progress Tracker Skill
Assess implementation progress of Airflow Improvement Proposals by comparing
what the Confluence spec promises against what the codebase delivers.
When to Use This Skill
Use this skill when the task involves:
- Tracking AIP implementation status
- Comparing a spec against shipped code
- Producing a cross-AIP progress report
Available Tools
You have access to these tools for gathering evidence:
fetch_confluence_page(page_id) -- fetch an AIP spec from Confluence
search_github_prs(query) -- search GitHub PRs/commits for an AIP
get_repo_file_tree(path_prefix) -- list files under a directory in the repo
Evidence Gathering Strategy
For each AIP, gather evidence from all three sources before assessing:
- Confluence spec -- call
fetch_confluence_page with the AIP's page ID.
Extract: deliverables, phases, completion criteria, and status.
- GitHub PRs and commits -- call
search_github_prs with both the AIP
number (e.g. "AIP-76") AND topic keywords (e.g. "asset partition").
Deduplicate results.
- Codebase file tree -- call
get_repo_file_tree with the AIP's known
directory prefixes. Count source files and test files.