autodev-specslisted

# specs-skill — GitHub Spec Kit document set Given a one-line requirement, create a numbered feature folder and fill it with the full Spec Kit artifact set, in phase order. Mirror `github/spec-kit`. Write real content grounded in the target repo — never leave a template placeholder. ## 0. Locate / create the folder - Scan `specs/` for the highest existing `NNN-*`. New folder = next number, zero-padded, kebab-slug of the requirement: `specs/NNN-slug/`. - If a complete matching spec already exists, update it in place — don't duplicate. ## 1. spec.md — the WHAT / WHY (no implementation detail) User scenarios as stories, numbered testable functional requirements (`FR-001 …`), key entities, and success / acceptance criteria. Mark every ambiguity with an explicit `[NEEDS CLARIFICATION: …]`. ## 2. plan.md — the HOW (technical, always present) Technical context (language, dependencies, storage, testing), a constitution / gate check, the concrete project structure, and a complexity section justifying any deviation from the simplest design. ## Phase 0 — research.md One block per unknown or decision: **Decision / Rationale / Alternatives considered**. Resolve every `[NEEDS CLARIFICATION]` from spec.md here. ## Phase 1 — design artifacts - **data-model.md** — entities, fields, types, relationships, validation rules, state transitions. - **contracts/** — one file per API / interface (OpenAPI, JSON-schema, or message shape). Omit only if the feature genuinely exposes no contract. -