project-status

Generate an evidence-based project status report by aggregating transcripts, local repositories, GitHub, and Linear data. This Skill cross-references these sources to distinguish discussed work from implemented work, outputting a component-by-component decision table with confidence levels.

Track implementation progress by evaluating multi-source evidence from transcripts, local repos, GitHub, and Linear. It applies evaluation rules to map each component's status—such as In Progress, In Review, or Done—into a comprehensive chart with descriptive evidence.

Yes, you can combine local repository files with Linear tickets and GitHub evidence to determine what is done and what is planned. The Skill synthesizes these sources to differentiate between discussed tasks and actual code implementations, providing clear status levels.

Combining transcripts and code repositories improves project status accuracy by validating discussed work against actual implemented code. This multi-source evaluation prevents false status reports by requiring real evidence from transcripts, local repos, GitHub, and Linear before assigning a status.

You need frontmatter with name and description, while repos.json and Linear configuration are optional dependencies. These configurations enable deeper multi-source evaluation across your local repositories and issue trackers to generate the final status decision table.

Supported status levels include Triage, Backlog, Todo, In Progress, In Review, Done, Shipped, Canceled, and Unknown. Each level is assigned based on aggregated evidence from transcripts, local repositories, GitHub, and Linear, accompanied by a descriptive evidence summary.