GitHub Copilot Workspace: from issue to code through an editable specification and plan
2024-04-29 · Publisher : GitHub · Domain : Methodology & Organization
GitHub opens a technical preview of Copilot Workspace, where AI starts from an issue, drafts a specification, proposes a step-by-step plan, then the code, with every step editable by the developer.
What changes
- The entry point is no longer the open file but the issue or pull request.
- Specification and plan become explicit artefacts, reviewed before the code.
- Tests and builds run in an integrated terminal before the pull request.
- A forerunner of 2025 spec-driven development.
### Background On 29 April 2024, **Thomas Dohmke**, then GitHub CEO, announced **Copilot Workspace**, born in GitHub Next. It is described as a "task-centric experience" chaining several Copilot-powered agents from idea to pull request. ### Key facts - Starts from a repository, an **issue** or a pull request. - Generates an editable **specification** describing the goal. - Step-by-step **plan** based on the codebase and the issue discussion; steps can be added, changed or annotated. - Changes shown as a diff, **integrated terminal** (Codespace) to run tests and builds, then a pull request. - Works on desktop and mobile; **technical preview** by sign-up. ### Why it matters GitHub formalised a split that became standard for agents: **intent, specification, plan, implementation**, with a human checkpoint at each step. The announcement states that "programming in natural language lowers the barrier of entry to who can build software". ### Takeaway Review moves upstream: before reading code, people read a specification and a plan. Kiro and Spec Kit picked up the idea a year later.
Links
Tags : Agents de code, Spécifications, GitHub