Roadmap

Phases, milestones and release objectives (design brief section 20). Status: draft, version 0.2.0. First versions of all 27 departments now exist: 267 skills (every candidate in the design brief, see data/candidate-skill-map.yaml), 7 programmes, 55 templates, 27 Copilot Cowork plugins and four reviewer-class departments with reviewer tests. Every skill is status: draft. The work ahead is review, evidence and hardening rather than new breadth.

Where we are

Next steps

1. Review every skill department by department and move reviewed skills from draft to reviewed.
2. Run the trigger tests behaviourally in Copilot Cowork and fix routing misses.
3. Produce the worked transformation pack for the fictional 600-person organisation and add the 5,000-person and regulated samples.
4. Exercise the reviewer tests for all four reviewer-class departments against real submissions.
5. Add source records for Copilot Code and refresh high-volatility product sources.
6. Publish the website at https://copilotforge.ai/ and gather beta feedback.

Definition of v1.0 (brief section 20.3)

• An unfamiliar user can create or supply a valid organisation profile.
• CopilotForge recommends an edition and maturity archetype with a clear rationale.
• The flagship acceptance prompt produces a coherent, internally consistent transformation pack.
• The same scenario produces proportionate recommendations for Starter and Enterprise contexts.
• Reviewer-class departments demonstrably block unsuitable outputs.
• Current product facts are traceable to source records.
• Golden scenarios and generated artefacts pass CI.
• The public website is generated from the repository and the programme builder works locally in the browser.
• A contributor can add a skill using documented conventions and receive actionable validation feedback.
• Copilot Cowork can perform a bounded maintenance task by following COWORK.md and the repository checks.

Department status