Spec-First Development With Copilot: A Current Alternative to Workspace
🔍 WiseChecker

Spec-First Development With Copilot: A Current Alternative to Workspace

Spec-first development means agreeing on observable behavior before authorizing implementation. Older guides attached this idea to Copilot Workspace, a GitHub Next experiment whose manual is now archived. You can apply the same discipline with current Copilot planning features without depending on the old preview interface.

Official documentation checked October 14, 2026.

Write a Small, Testable Specification

Create a document in your repository that states the problem, intended users, inputs, outputs and acceptance criteria. Include what must not change. For example, a CSV-import feature might need to preserve leading zeros in account IDs, report malformed rows without silently skipping them, and leave the source file untouched.

Separate requirements from implementation suggestions. “Preserve leading zeros” is a requirement; “use a particular CSV library” is a design choice unless the project already mandates it. Record unresolved questions so the agent cannot silently decide them.

Ask for a Plan Before Changes

  1. Open the correct project in VS Code and start a new Chat session.
  2. Select the intended session target and use /plan with the specification and constraints. The official planning guide distinguishes Copilot Plan mode from the Local Plan agent and describes their controls.
  3. Ask the agent to identify affected files, dependencies, compatibility risks and the tests that will demonstrate each requirement.
  4. Read the full plan. Correct assumptions, unnecessary changes and missing test cases before approving implementation.

Example request: “Plan the CSV import described in this specification. Preserve source files and existing export behavior. Identify ambiguous requirements. Do not implement until I approve the plan.” Use the actual planning mode and permissions as well; prose alone is not an access-control boundary.

Implement, Then Verify Against the Specification

Keep a version-control checkpoint before implementation. Use the planning interface’s supported implementation action only after reviewing the plan and its permission settings. Review the diff, run the project checks and test the acceptance cases independently.

For each requirement, record a result: passed with evidence, failed, or not tested. If the code fails, ask for a correction to that specific condition rather than redefining the requirement to fit the output. If the specification changes, update it explicitly and repeat the relevant checks.

A plan is not proof of working software, and generated tests can share the same mistaken assumption as the implementation. Include at least one independently chosen edge case. Save the final specification and validation notes with the change so a later reviewer can see why the implementation is acceptable.

ADVERTISEMENT

Did this guide solve your problem?