project-tracker

# Project tracker Read the routed canonical `runbooks/project-tracker.md` before acting. If it is unavailable locally, read the [public tracker runbook](https://github.com/z-shell/.github/blob/main/runbooks/project-tracker.md). It owns tracker identity, inclusion, field and relationship policy, reconciliation and managed progress. If neither source is accessible, report the gap and do not perform external writes. - Resolve the owning issues or pull requests and the requested tracker operation, then select the relevant runbook steps. Use its linked triage procedure for authority and issue disposition. - Discover installed MCP, app or CLI capabilities and current command help; do not assume a tool contract or refresh credentials merely because a write is requested. - Inspect current membership, field definitions, values and relevant workflow effects before proposing changes. Report incomplete pagination or unavailable evidence; do not infer automatic transitions from workflow names. - Apply only the approved targets and mutations. Tool availability, this skill and reconciliation capability grant no additional authority; preserve human-set fields outside that scope. - Use the runbook's existing reconciliation tools when applicable. Follow its privacy and verification limits; membership counts alone do not establish portfolio readiness. - Read stored membership and fields back after authorized writes, and record progress, blockers or handoff on the owning work records as the runbook requires.