docs: Initialize Spec Kit + ratify constitution v0.0.1

[SayefReyadh]

Summary

Initializes Spec Kit for spec-driven development per the Spec-Driven Development Standard and Agentic SDLC.

What's included

• .specify/memory/constitution.md — Project constitution (v0.0.1) with service-specific principles, connected services map, known system behaviors, and governance
• .specify/templates/*.md — 5 templates used by Spec Kit skills (spec, plan, tasks, checklist, constitution)
• .specify/feature.json — Active spec pointer
• .claude/skills/speckit-*/ — 9 core Spec Kit skills for Claude Code (/speckit-specify, /speckit-plan, /speckit-tasks, /speckit-implement, /speckit-constitution, /speckit-clarify, /speckit-analyze, /speckit-checklist, /speckit-taskstoissues)

What was intentionally removed

The initial specify init scaffolded ~50 files. We removed 34 unnecessary files to keep the setup lean:

• .specify/scripts/ — bash + PowerShell helpers (not used by Claude Code skills)
• .specify/extensions/ — git extension with auto-branch/commit scripts (we handle git manually)
• .specify/workflows/ — workflow YAML (skills work independently)
• .specify/integrations/ — manifest bookkeeping files
• .specify/extensions.yml, init-options.json, integration.json — config/bookkeeping
• 5 git automation skills (speckit-git-*) that depended on the removed scripts

Constitution highlights

The constitution is tailored to this service with:

• 5-7 principles specific to the service's architecture and constraints (not generic filler)
• Connected Services table mapping upstream/downstream services with data flow descriptions
• Known System Behaviors section documenting service-specific gotchas
• Cross-service peer references where applicable (e.g., edge Workers referencing each other)
• Governance with semantic versioning for amendments

How to use

After merging, the Spec Kit workflow is available via Claude Code slash commands:

1. /speckit-specify <description> — Define what to build (creates spec.md)
2. /speckit-plan — Research codebase + create technical plan (plan.md)
3. /speckit-tasks — Break into vertical slices (tasks.md)
4. /speckit-implement — Execute the tasks

Optional: /speckit-clarify (de-risk ambiguity), /speckit-analyze (consistency check), /speckit-checklist (quality validation).

Test plan

• Constitution has no placeholder tokens
• All principles are specific to this service
• Connected services match known data flow patterns
• Known System Behaviors section present
• 9 core speckit skills registered
• Unnecessary scaffold files removed (34 files)

🤖 Generated with Claude Code