Copilot Skill: spec-scaffold

# Copilot Skill: spec-scaffold

## Intent

Generate numbered spec folders with `requirements.md`, `plan.md`, and `tasks.md` for repo work that needs a clear implementation path before coding.

Use this skill when the user wants to turn a rough feature, fix, migration, or repo maintenance idea into a concrete spec package.

## Use When

- The user asks to create a spec
- The work has enough complexity to benefit from requirements, plan, and tasks
- The repo uses numbered spec folders
- The user wants an implementation checklist before code changes

## Do Not Use When

- The request is a tiny one-file change
- The user wants implementation immediately and no spec
- The task is only a commit message, PR review, or README audit

## Workflow

1. Read the user's request and any repo context.
2. Propose a kebab-case spec slug.
3. Use the next numbered folder if the repo already has a `specs/` directory.
4. Create or draft these files:
   - `requirements.md`
   - `plan.md`
   - `tasks.md`
5. Keep requirements testable and implementation-neutral.
6. Keep the plan practical and repo-aware.
7. Keep tasks ordered and checkable.

## Folder Format

Use this shape: