Copilot customization workshop

Appearance

09 — Optional Spec-Kit: unavailable in this release ​

Goal and starting workspace ​

  • Reference-only, consumer or browser. Core 00–08 does not depend on Spec-Kit.
  • No genuine Spec-Kit generation was performed; no generated artifacts, version, command transcript, or provenance are claimed.

Build it yourself ​

  • This release offers no executable Spec-Kit walkthrough. Use the existing tool-neutral contract/brief/tests.
  • A future owner-approved extension must pin the real generator version, run documented commands in an isolated area, preserve genuine spec/plan/tasks and generation metadata, and review all generated customizations before activation.
  • Participants need no Python/uv install for current core labs.

Inspect the example ​

Bring in this step ​

sh
# CONSUMER; optional status notice only
npm run lab:example -- --step 09-spec-kit --preview
npm run lab:example -- --step 09-spec-kit --stage
npm run lab:example -- --step 09-spec-kit --apply

If you already changed these files ​

  • Preserve real future generation/evidence; stage this release's notice separately. Never overwrite core specifications or activate generated prompts automatically.

Client steps ​

VS Code ​

  • Read the notice and core specification. No Spec-Kit command/prompt discovery is asserted.

Copilot CLI ​

  • Read-only core comparison is available; no generated slash command or setup route is invented.

Copilot app ​

  • Browser/artifact reading only. No native generator or plugin-install route is claimed.

Verify the result ​

  • npm run verify:exercise -- --step 09-spec-kit verifies notice presence, not Spec-Kit support.
  • Record unavailable — not generated. Recovery is to continue core labs, not fabricate tool output.