Organize R&D work into SRED-compliant project documents

Turns a prior-year work summary (produced by a companion sred-work-summary skill) into SRED-formatted project documentation in Notion, with one child document per SREDable project. It reads the Work Summary Notion document (a list of projects each with its PRs, Notion docs, and Linear tickets), evaluates every project against a reference SRED-project description to classify it as "SREDable" or not - erring toward classifying more projects as SRED-eligible where the work genuinely fits - then confirms that classification with the user before proceeding. For each SREDable project it creates a child "SRED Project Summary" document from a fixed template: a Project Description and Project Goals section (each capped at 100 words, drawn from the Work Summary and the project's own Notion docs), a set of Technical Uncertainties (each a genuine unanswered challenge or problem, described in a few sentences, with its own Experiments and Results/Learnings/Success bullet lists and links), and a Project Documentation and Links section listing every remaining project link not already attached to a specific uncertainty. At each major step it shows the user what it produced - the Uncertainties, then the completed Project Summary - and asks for review and corrections before moving to the next project.

Use it when a prior-year work summary needs to become SRED-formatted project documents, when projects need to be classified as SREDable with supporting evidence collected, or when the output needs to land organized in Notion. It depends on already having, or being ready to generate, the upstream Work Summary document this organizer consumes. GitHub, Notion, and Linear must be reachable before starting - Notion and Linear connected via MCP, and GitHub either via MCP or the gh CLI - and the skill should prompt the user to grant access rather than proceed without it if any of the three is unavailable.

Input is a linked Notion Work Summary document listing, per project, its pull requests, Notion docs, and Linear tickets with dates, plus two reference files: SRED.md (what qualifies as a SRED project) and project-template.md (the per-project document template). Output is a private "SRED Project Descriptions" parent Notion document plus one private "SRED Project Summary - <year> <project name>" child document per SREDable project, each containing a Project Description, Project Goals, a Technical Uncertainties section (with Experiments, Results/Learnings/Success, and uncertainty-specific links per uncertainty), a Project Documentation and Links section for remaining links, and a Participants section the user fills in - with the full Notion link to both the parent document and each project summary handed back to the user for review.

Reads and cross-references GitHub pull requests, Notion documents, and Linear tickets to gather evidence, and writes its output as structured Notion documents; GitHub access can go through either an MCP connector or the gh CLI directly, while Notion and Linear are expected to be connected via MCP.

Teams preparing SR&ED (Scientific Research and Experimental Development) tax-credit documentation who need last year's engineering work turned into properly structured project summaries - description, goals, technical uncertainties, experiments, and evidence links - without manually assembling each document by hand.