Catalogue › Copilot Code
CopilotForge - Copilot Code
Use it in Copilot Cowork: download the Copilot Code plugin for Copilot Cowork and upload it under Customize > Plugins > Upload plugin. How to install.
Translate desired outcomes into governed software prototypes and production-ready engineering work.
- Layer: delivery
- Lead role: Engineering Lead
- Plugin name:
copilotforge-copilot-code
| Skill | Status | Lifecycle | Description |
|---|---|---|---|
ai-assisted-prototyping | draft | Discover, Envision, Deliver | Sets the boundaries for prototyping with Copilot Code - a question, a time box, a sandbox, safe data, no production connections and an end decision to discard, rebuild or promote - so quick prototypes never become unowned software. Use when a team wants to try an idea in code with AI, when a prototype has started being used for real, or when sponsors ask how to encourage experiments safely. |
application-validation | draft | Assure, Launch | Validates an application built with Copilot Code against its solution brief, tracing every acceptance criterion to reviewed tests, negative and edge cases, non-functional checks and business owner acceptance, and records a pass, conditional pass or fail. Use when an AI-built application is feature-complete, when a business owner must accept a build, or when generated tests look thorough but nobody has checked them against requirements. |
code-deployment-readiness | draft | Assure, Launch | Checks that an AI-built application is ready to deploy and run - validated, security-reviewed, deployed through a pipeline to approved hosting, with least-privilege identity, monitoring, a rollback plan, a support route, named owners and recorded release approval for its risk tier. Use when an AI-built application is about to go live, when a prototype is being promoted, or when an application is running somewhere nobody approved. |
code-solution-brief | draft | Envision, Deliver | Writes the solution brief that frames an AI-assisted software build - outcome, users, scope and exclusions, data and systems touched, constraints and non-functional needs, acceptance criteria, owners and route to production - so the coding agent and reviewers work to one agreed definition. Use when a Copilot Code build has been approved, when a prototype is being promoted, or when a build is drifting because nobody wrote down what it is for. |
code-use-case-assessment | draft | Envision, Deliver | Assesses whether a desired outcome genuinely needs software built with Copilot Code, or is better met by configuration, an existing product, a Power Platform app or flow, an agent, a Cowork task or no build, and whether the organisation can own what gets built. Use when a business team asks AI to build them an app or script, when a prototype is proposed, or when someone asks why not just have AI write it. |
generated-code-review | draft | Deliver, Assure | Sets and applies code review standards for changes produced by an AI coding agent - reviewable size, understanding before approval, tests checked against the work item, conventions and no unnecessary changes - so human review stays meaningful at agent speed. Use when a team starts accepting agent pull requests, when reviews have become rubber stamps, or when generated changes are merging that nobody on the team can explain. |
generated-code-security-review | draft | Assure, Launch | Reviews AI-generated code for weaknesses coding agents commonly introduce - injection, broken authorisation, secrets, unsafe dependencies, broad permissions and data leakage - and classifies each finding as blocking or advisory with a fix. Use when an AI-built application or significant generated change nears release, when generated code touches identity or data access, or when a new dependency was added by the agent. |
maintainability-review | draft | Measure, Scale, Improve | Reviews whether an AI-built application can be understood, changed and kept secure by people over its life - ownership, comprehension without the agent, documentation, tests, dependency upkeep and spread of knowledge - and recommends keep, invest, consolidate or retire. Use when an AI-built application reaches its scheduled review, when its owner is leaving, or when a growing estate of AI-built tools needs triage. |
repository-context | draft | Mobilise, Deliver, Improve | Prepares the repository context an AI coding agent works within - custom instructions, conventions, architecture notes, approved dependencies, protected areas, test commands and never-touch rules - so generated changes follow the organisation's standards. Use when a repository is first opened to a coding agent, when agent output keeps ignoring conventions, or when a team asks how to stop the agent touching secrets or sensitive code. |
requirements-to-build | draft | Deliver | Turns an agreed solution brief into small, ordered, testable work items an AI coding agent and its human reviewers can deliver - each with a clear outcome, acceptance tests, boundaries and dependencies - so generated changes stay reviewable. Use when a Copilot Code build is about to start, when agent-generated pull requests are too large to review, or when work items keep coming back because acceptance was unclear. |
Credit
Created by Simon Foote as part of CopilotForge. Content is licensed under CC BY 4.0; keep the credit in each skill's license and authors fields when you share or adapt it. See NOTICE.md in the repository.