[P0][Tier 3] Add a spec-first / plan-first playbook with reviewable plans

Open
#3,283 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
developer-experience, documentation

Research direction

Start by reading the existing v2-migration.prompt.md and docs/v2/v2-planning.md workflows, then locate the context entry point where the new guidance should be referenced. Add a general spec-first/plan-first playbook and plan template covering the listed planning and review fields. Done means both are discoverable from the context entry point and the template supports review before implementation.

Written by the indexing model from the issue text.

Description

AIEngineering

Tier 3 — Workflow adoption · Priority: P0

Gap

There are point workflows (v2-migration.prompt.md, docs/v2/v2-planning.md) but no general spec-first/plan-first playbook for non-trivial work. Plans do not consistently define scope, non-goals, affected areas, acceptance criteria, validation, and review expectations, and are not reliably reviewable before a large diff appears.

Investment
  • Add a spec-first/plan-first playbook + plan template (scope, non-goals, affected areas, acceptance criteria, validation, review expectations).
  • Keep planning and implementation separable so the plan can be approved before execution.
Acceptance criteria
  • Playbook + plan template exist and are referenced from the context entry point.
  • Plan template carries context into implementation and can be reviewed before the diff.

Part of epic #3273

Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-dotnettools

All issues in microsoft/vscode-dotnettools

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.