メニュー
Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement an approved spec end-to-end in the pickup-points-modal repo — branch, code, tests, lint, typecheck, build, commit, and open a PR following Conventional Commits and the project constitution.
Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.
Generate a per-feature validation checklist (pre-merge gates, manual QA steps, rollback plan) for a pickup-points-modal feature, tailored to the spec and constitution principles.
Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.
Create or amend the project constitution in .specify/memory/constitution.md, capturing binding principles, governance, and ratification metadata for the pickup-points-modal.
Compose Conventional Commits messages and stage the right files for a pickup-points-modal change, respecting CHANGELOG and the constitution's backward-compat principle.
| name | specification |
| description | Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written. |
| type | skill |
Use this skill when the user asks to "create a spec", "write an SDD", or
references a file under specs/. The deliverable is a
specs/<feature-slug>/spec.md file with three mandatory sections.
PickupPointsModal.Do not use for a one-off bug fix or a styling tweak — go straight to
implementing or speckit-git-commit.
# Spec: <feature>
## Business Context
- Problem being solved
- Stakeholders (who asked, who is impacted)
- Success metrics
## Architectural Decisions
- Components/files affected
- Alternatives considered + why they were dropped
- Backward-compatibility risk (cite Principle 1 of the constitution)
## Technical Contract
- Changes to props/events
- Changes to fixtures/mocks
- Test plan (golden path + edge cases)
- i18n plan (new keys, locales touched)
- Verifiable acceptance criteria
TBD markers where input is missing.