{"id":"0d9e72c1-66de-4f02-9492-8072b8200f5b","entityType":"agent","slug":"clawhub-athola-nm-spec-kit-speckit-orchestrator","name":"speckit-orchestrator","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-spec-kit-speckit-orchestrator","canonicalPath":"/agent/clawhub-athola-nm-spec-kit-speckit-orchestrator","generatedAt":"2026-10-10T08:48:12.255Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":null},"description":"Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Skill: speckit-orchestrator Owner: athola Summary: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:23:14.767Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:43:01.385Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:59:51.620Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:07:14.088Z | user Release v1.9.14 v1.9.13 | 2026-06-2","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.7K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-spec-kit-speckit-orchestrator","sourceUrl":"https://clawhub.ai/athola/nm-spec-kit-speckit-orchestrator","homepage":"https://clawhub.ai/athola/skills/nm-spec-kit-speckit-orchestrator","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-spec-kit-speckit-orchestrator","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-spec-kit-speckit-orchestrator","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":65,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Skill: speckit-orchestrator Owner: athola Summary: Orchestrates Spec Driven Dev"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":null},"stars":null,"forks":null,"downloads":1686,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.7K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T04:27:51.024Z","lastCrawledAt":"2026-10-10T04:27:51.024Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T04:27:51.024Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:23:14.767Z","changelog":"Release v1.9.19","fileCount":7,"zipByteSize":13510},{"version":"1.9.17","createdAt":"2026-07-30T05:43:01.385Z","changelog":"Release v1.9.17","fileCount":7,"zipByteSize":13554},{"version":"1.9.16","createdAt":"2026-07-14T19:59:51.620Z","changelog":"Release v1.9.16","fileCount":7,"zipByteSize":13429},{"version":"1.9.14","createdAt":"2026-06-30T18:07:14.088Z","changelog":"Release v1.9.14","fileCount":7,"zipByteSize":13578},{"version":"1.9.13","createdAt":"2026-06-27T16:25:03.553Z","changelog":"Release v1.9.13","fileCount":7,"zipByteSize":13588},{"version":"1.9.12","createdAt":"2026-06-19T03:20:53.030Z","changelog":"Release v1.9.12","fileCount":7,"zipByteSize":13442},{"version":"1.0.2","createdAt":"2026-05-09T02:20:46.568Z","changelog":"Release v1.9.5","fileCount":7,"zipByteSize":13709},{"version":"1.0.1","createdAt":"2026-05-06T14:22:16.970Z","changelog":"Release v1.9.4","fileCount":6,"zipByteSize":12468}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-spec-kit-speckit-orchestrator","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T08:48:12.252Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":null},"readme":"Skill: speckit-orchestrator\n\nOwner: athola\n\nSummary: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:23:14.767Z | user\n\nRelease v1.9.19\n\nv1.9.17 | 2026-07-30T05:43:01.385Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:59:51.620Z | user\n\nRelease v1.9.16\n\nv1.9.14 | 2026-06-30T18:07:14.088Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:25:03.553Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:20:53.030Z | user\n\nRelease v1.9.12\n\nv1.0.2 | 2026-05-09T02:20:46.568Z | user\n\nRelease v1.9.5\n\nv1.0.1 | 2026-05-06T14:22:16.970Z | user\n\nRelease v1.9.4\n\nv1.0.0 | 2026-04-20T16:01:48.786Z | auto\n\nVersion 1.0.0 – Initial release.\n\n- Introduces speckit-orchestrator: coordinates Spec Driven Development workflows and tracks progress.\n- Handles session initialization, skill loading, and workflow phase tracking for speckit projects.\n- Provides command-skill mapping and progress tracking items.\n- Integrates with related skills for specification, planning, brainstorming, and executing plans.\n- Includes usage guidance, troubleshooting tips, and exit criteria.\n\nArchive index:\n\nArchive v1.9.19: 7 files, 13510 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5698b), modules/writing-plans-extensions.md (8735b), skill-card.md (2209b), SKILL.md (4533b), _meta.json (152b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: speckit-orchestrator\ndescription: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\nversion: 1.9.8\ntriggers:\n - speckit\n - workflow\n - orchestration\n - planning\n - specification\n - running the full speckit workflow from spec to implementation\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.superpowers:brainstorming\", \"night-market.superpowers:writing-plans\", \"night-market.superpowers:executing-plans\"]}}}\nsource: claude-night-market\nsource_plugin: spec-kit\n---\n\n> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Persistent Presence Lens](#persistent-presence-lens)\n- [When to Use](#when-to-use)\n- [Core Workflow](#core-workflow)\n- [Session Initialization](#session-initialization)\n- [Command-Skill Matrix](#command-skill-matrix)\n- [Progress Tracking Items](#progress-tracking-items)\n- [Exit Criteria](#exit-criteria)\n- [Related Skills](#related-skills)\n\n\n# Speckit Orchestrator\n\n## Overview\n\nCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.\n\n## Persistent Presence Lens\n\nTreat SDD as a minimal, testable \"self-modeling\" loop:\n\n- **World model**: repo + speckit artifacts (`spec.md`, `plan.md`, `tasks.md`)\n- **Agent model**: loaded skills/plugins + constraints (especially `.specify/memory/constitution.md`) + progress state\n\nThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (`tasks.md`) and a skill library (reusable plugin skills and superpowers methodology skills).\n\n## When To Use\n\n- Starting any `/speckit-*` command.\n- Coordinating multi-phase development workflows.\n- Tracking progress across specification, planning, and implementation.\n- Ensuring skill dependencies are loaded.\n\n## When NOT To Use\n\n- Single-phase work (just specify, or just plan)\n- Non-spec-driven projects\n\n## Core Workflow\n\n### Session Initialization\n\n1. **Verify Repository Context**\n - Confirm working directory is a speckit-enabled project.\n - Check for `.specify/` directory structure.\n - Validate required scripts exist.\n\n2. **Load Persistent State (\"presence\")**\n - Read `.specify/memory/constitution.md` for constraints/principles.\n - Load current `spec.md` / `plan.md` / `tasks.md` context if present.\n\n3. **Load Command Dependencies**\n - Match current command to required skills.\n - Load complementary superpowers skills.\n\n4. **Initialize Progress Tracking**\n - Create TodoWrite items for workflow phases.\n - Track completion status.\n\n### Command-Skill Matrix\n\nQuick reference for command-to-skill mappings:\n\n| Command | Primary Skill | Complementary Skills |\n|---------|--------------|---------------------|\n| `/speckit-specify` | spec-writing | brainstorming |\n| `/speckit-clarify` | spec-writing | brainstorming |\n| `/speckit-plan` | task-planning | writing-plans |\n| `/speckit-tasks` | task-planning | executing-plans |\n| `/speckit-implement` | - | executing-plans, systematic-debugging |\n| `/speckit-analyze` | - | systematic-debugging, verification |\n| `/speckit-checklist` | - | verification-before-completion |\n\n**For detailed patterns**: See `modules/command-skill-matrix.md` for complete mappings and loading rules.\n\nSee `modules/writing-plans-extensions.md` for plan authoring patterns.\n\n### Progress Tracking Items\n\nFor each workflow session, track:\n- [ ] Repository context verified.\n- [ ] Prerequisites validated.\n- [ ] Command-specific skills loaded.\n- [ ] Artifacts created/updated.\n- [ ] Verification completed.\n\n**For detailed patterns**: See `modules/progress-tracking.md` for TodoWrite patterns and metrics.\n\n## Exit Criteria\n\n- Active command completed successfully.\n- All required artifacts exist and are valid.\n- Progress tracking reflects current state.\n- No unresolved blockers.\n\n## Related Skills\n\n- `spec-writing`: Specification creation and refinement.\n- `task-planning`: Task generation and planning.\n- `superpowers:brainstorming`: Idea refinement.\n- `superpowers:writing-plans`: Implementation planning.\n- `superpowers:executing-plans`: Task execution.\n\nFile v1.9.19:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-spec-kit-speckit-orchestrator\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787750594767\n}\n\nFile v1.9.19:modules/artifact-structure.md\n\n---\nname: artifact-structure\ndescription: Documentation of spec-kit artifact structure, purposes, and organization\ncategory: reference\ntags: [artifacts, structure, organization, documentation]\ndependencies: [speckit-orchestrator]\ncomplexity: beginner\nestimated_tokens: 800\n---\n\n# Spec-Kit Artifact Structure\n\n## Overview\n\nSpec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.\n\n## Directory Structure\n\n```\nproject-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/\n```\n\n> **Note: Claude Code Plan Mode Namespace**\n>\n> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the\n> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.\n> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid\n> collision. When searching for scope artifacts:\n> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)\n> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)\n>\n> The two systems are complementary: Claude Plan Mode is for exploratory planning,\n> while spec-kit plans are structured implementation blueprints.\n\n## Core Artifacts\n\n### spec.md - Feature Specification\n\n**Purpose**: Define WHAT users need and WHY, without implementation details.\n\n**Audience**: Business stakeholders, product managers, non-technical reviewers.\n\n**Structure**:\n```markdown\n# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Technology-agnostic metrics\n- User-facing goals\n\n## Success Criteria (Optional)\n- Performance expectations\n- Security considerations\n- Accessibility needs\n\n## Edge Cases (Optional)\n- Boundary conditions\n- Error scenarios\n- Fallback behaviors\n\n## Dependencies & Assumptions (Optional)\n- External dependencies\n- Documented assumptions\n```\n\n**Key Principles**:\n- No technology choices (no \"React\", \"PostgreSQL\", \"REST API\")\n- Focus on user value, not system internals\n- Measurable, testable requirements\n- Maximum 3 [NEEDS CLARIFICATION] markers\n\n### plan.md - Implementation Plan\n\n**Purpose**: Define HOW to build the feature technically.\n\n**Audience**: Developers, technical leads, architects.\n\n**Structure**:\n```markdown\n# Implementation Plan: Feature Name\n\n## Technical Context\n- Tech stack decisions\n- Architecture choices\n- Libraries and frameworks\n\n## Constitution Check\n- Alignment with project principles\n- Gate evaluation\n\n## Phase 0: Research\n- Technical unknowns\n- Best practices research\n- Decision rationale\n\n## Phase 1: Design\n- Data model\n- API contracts\n- Integration points\n\n## Phase 2: Implementation\n- Component structure\n- Service layer\n- Infrastructure needs\n```\n\n**Key Principles**:\n- Technology-specific\n- Includes research and decisions\n- Maps to project constitution\n- Generates tasks.md\n\n### tasks.md - Implementation Tasks\n\n**Purpose**: Actionable, dependency-ordered tasks for implementation.\n\n**Audience**: Developers executing the feature.\n\n**Structure**:\n```markdown\n# Implementation Tasks: Feature Name\n\n## Overview\n- Total tasks\n- Parallelization opportunities\n- MVP scope\n\n## Dependencies\n- User story completion order\n- Blocking prerequisites\n\n## Phase 1: Setup\n- [ ] T001 Project initialization\n- [ ] T002 [P] Configure tooling\n\n## Phase 2: Foundational\n- [ ] T010 Shared infrastructure\n\n## Phase 3: User Story 1 (P1)\n- [ ] T020 [US1] Model creation\n- [ ] T021 [P] [US1] Service implementation\n- [ ] T022 [US1] Endpoint implementation\n\n## Phase 4: User Story 2 (P2)\n- [ ] T030 [US2] Feature implementation\n\n## Final Phase: Polish\n- [ ] T090 Cross-cutting concerns\n- [ ] T091 Documentation\n```\n\n**Task Format**:\n```\n- [ ] [TaskID] [P?] [Story?] Description with file path\n```\n\n**Key Principles**:\n- Organized by user story\n- Sequential task IDs\n- Clear parallelization markers [P]\n- Story labels [US1], [US2], etc.\n- Explicit file paths\n\n### checklists/ - Quality Validation\n\n**Purpose**: \"Unit tests for requirements\" - validate requirement quality.\n\n**Audience**: Spec authors, reviewers, QA.\n\n**Structure**: Multiple domain-specific checklists:\n- `requirements.md` - Overall spec quality\n- `ux.md` - UX requirements validation\n- `api.md` - API requirements validation\n- `security.md` - Security requirements validation\n- `performance.md` - Performance requirements validation\n\n**Checklist Item Format**:\n```markdown\n- [ ] CHK001 Are [requirements] defined for [scenario]? [Dimension, Reference]\n```\n\n**Key Principles**:\n- Test requirements quality, NOT implementation\n- Focus on completeness, clarity, consistency\n- ≥80% traceability to spec sections\n- Question format, not verification statements\n\n## Supporting Artifacts\n\n### research.md\nDocuments technical research, decisions, and alternatives considered during Phase 0.\n\n### data-model.md\nDefines entities, fields, relationships, validation rules, and state transitions.\n\n### quickstart.md\nTest scenarios and acceptance testing guides for the feature.\n\n### contracts/\nAPI contracts (OpenAPI, GraphQL schemas) generated from functional requirements.\n\n## Workflow Progression\n\n1. **Specify**: Create spec.md (user-focused, no tech)\n2. **Clarify**: Resolve [NEEDS CLARIFICATION] markers\n3. **Checklist**: Validate spec quality with requirements.md checklist\n4. **Plan**: Create plan.md (technical design)\n5. **Tasks**: Generate tasks.md (actionable implementation)\n6. **Implement**: Execute tasks, mark complete\n7. **Validate**: Domain-specific checklists (ux.md, api.md, etc.)\n\n## Artifact Relationships\n\n```\nspec.md (WHAT/WHY)\n ↓\nchecklists/requirements.md (validate spec)\n ↓\nplan.md (HOW)\n ↓\ntasks.md (DO)\n ↓\nchecklists/[domain].md (validate implementation requirements)\n```\n\n## Usage in Commands\n\n- `/speckit-specify` → Creates spec.md, checklists/requirements.md\n- `/speckit-clarify` → Resolves [NEEDS CLARIFICATION] in spec.md\n- `/speckit-plan` → Creates plan.md, research.md, data-model.md, contracts/\n- `/speckit-tasks` → Generates tasks.md from plan.md + spec.md\n- `/speckit-checklist` → Creates domain-specific checklists (ux.md, api.md, etc.)\n- `/speckit-implement` → Executes tasks.md\n- `/speckit-analyze` → Cross-artifact consistency validation\n\nFile v1.9.19:modules/command-skill-matrix.md\n\n# Command-Skill Matrix\n\n## Overview\n\nThe Command-Skill Matrix defines which skills are required for each speckit command, ensuring proper dependencies are loaded and coordinated throughout the workflow.\n\n## Complete Mapping\n\n### Specification Phase\n\n**`/speckit-specify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: At command start, before any specification work\n- **Purpose**: Create or refine feature specifications with collaborative ideation\n\n**`/speckit-clarify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: When specification needs refinement or has gaps\n- **Purpose**: Identify underspecified areas and encode clarifications\n\n**`/speckit-constitution`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: None required\n- **Loading Order**: spec-writing only\n- **When to Load**: Creating or updating project principles\n- **Purpose**: Establish project governance and design principles\n\n### Planning Phase\n\n**`/speckit-plan`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:writing-plans`\n- **Loading Order**: task-planning → writing-plans\n- **When to Load**: After specification is complete\n- **Purpose**: Generate detailed implementation design artifacts\n\n**`/speckit-tasks`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:executing-plans`\n- **Loading Order**: task-planning → executing-plans\n- **When to Load**: After planning artifacts exist\n- **Purpose**: Generate dependency-ordered implementation tasks\n\n### Implementation Phase\n\n**`/speckit-implement`**\n- **Primary Skill**: None (uses loaded plan)\n- **Complementary Skills**: `superpowers:executing-plans`, `superpowers:systematic-debugging`\n- **Loading Order**: executing-plans → systematic-debugging (on-demand)\n- **When to Load**: When executing tasks from tasks.md\n- **Purpose**: Execute implementation tasks with error handling\n\n### Verification Phase\n\n**`/speckit-analyze`**\n- **Primary Skill**: None (analysis only)\n- **Complementary Skills**: `superpowers:systematic-debugging`, `superpowers:verification-before-completion`\n- **Loading Order**: Load both at analysis start\n- **When to Load**: After task generation or implementation\n- **Purpose**: Cross-artifact consistency and quality analysis\n\n**`/speckit-checklist`**\n- **Primary Skill**: None (generation only)\n- **Complementary Skills**: `superpowers:verification-before-completion`\n- **Loading Order**: verification-before-completion only\n- **When to Load**: When generating feature-specific checklists\n- **Purpose**: Create custom verification checklists\n\n**`/speckit-startup`**\n- **Primary Skill**: None (bootstrap only)\n- **Complementary Skills**: None required\n- **Loading Order**: N/A\n- **When to Load**: Session initialization\n- **Purpose**: Bootstrap workflow and verify environment\n\n## Skill Loading Priorities\n\n### High Priority (Always Load First)\n1. `spec-writing` - For any specification work\n2. `task-planning` - For any planning work\n\n### Medium Priority (Load After Primary)\n3. `superpowers:brainstorming` - For ideation phases\n4. `superpowers:writing-plans` - For detailed planning\n5. `superpowers:executing-plans` - For implementation\n\n### Low Priority (Load On-Demand)\n6. `superpowers:systematic-debugging` - When errors occur\n7. `superpowers:verification-before-completion` - For final checks\n\n## Conditional Loading Rules\n\n- **Brainstorming**: Only load if specification is new or incomplete\n- **Systematic Debugging**: Only load if implementation encounters errors\n- **Verification**: Only load for analyze/checklist commands or before completion\n- **Writing Plans**: Only load if creating new implementation plans\n\n## Skill Interaction Patterns\n\n### Specification → Planning\n- Specification skills complete → task-planning loads\n- Hand off spec.md to planning phase\n\n### Planning → Implementation\n- Planning skills complete → executing-plans loads\n- Hand off tasks.md to implementation phase\n\n### Implementation → Verification\n- Implementation errors → systematic-debugging loads\n- Implementation complete → verification-before-completion loads\n\nFile v1.9.19:modules/progress-tracking.md\n\n# Progress Tracking\n\n## Overview\n\nDefines TodoWrite item patterns and progress tracking strategies for speckit workflows. validates consistent status reporting and verification throughout all workflow phases.\n\n## TodoWrite Item Patterns\n\n### Universal Workflow Items\n\nFor every speckit command session:\n\n```\n- [ ] Verify repository context and .specify/ structure\n- [ ] Validate prerequisites (scripts, dependencies, templates)\n- [ ] Load command-specific skills\n- [ ] Execute command workflow\n- [ ] Verify artifacts created/updated\n- [ ] Complete progress tracking\n```\n\n### Specification Phase Items\n\n**`/speckit-specify`**\n```\n- [ ] Load spec-writing and brainstorming skills\n- [ ] Analyze feature description and requirements\n- [ ] Generate/update spec.md with template\n- [ ] Verify spec.md contains all required sections\n- [ ] Validate frontmatter metadata\n```\n\n**`/speckit-clarify`**\n```\n- [ ] Read existing spec.md\n- [ ] Identify underspecified areas\n- [ ] Ask targeted clarification questions (max 5)\n- [ ] Encode answers back into spec.md\n- [ ] Verify improved specification completeness\n```\n\n**`/speckit-constitution`**\n```\n- [ ] Gather project principles (interactive or provided)\n- [ ] Create/update constitution.md\n- [ ] Sync dependent templates with constitution\n- [ ] Verify template consistency\n```\n\n### Planning Phase Items\n\n**`/speckit-plan`**\n```\n- [ ] Load task-planning and writing-plans skills\n- [ ] Read spec.md and constitution.md\n- [ ] Execute planning template workflow\n- [ ] Generate plan.md with design artifacts\n- [ ] Verify plan completeness and consistency\n```\n\n**`/speckit-tasks`**\n```\n- [ ] Read all available design artifacts (spec, plan, constitution)\n- [ ] Analyze dependencies and ordering constraints\n- [ ] Generate tasks.md with concrete tasks\n- [ ] Verify task ordering and completeness\n- [ ] Mark tasks ready for implementation\n```\n\n### Implementation Phase Items\n\n**`/speckit-implement`**\n```\n- [ ] Load executing-plans skill\n- [ ] Read and parse tasks.md\n- [ ] Execute tasks in dependency order\n- [ ] Track completion status per task\n- [ ] Handle errors with systematic-debugging\n- [ ] Verify all tasks completed successfully\n```\n\n### Verification Phase Items\n\n**`/speckit-analyze`**\n```\n- [ ] Read spec.md, plan.md, tasks.md\n- [ ] Check cross-artifact consistency\n- [ ] Identify quality issues\n- [ ] Generate analysis report\n- [ ] Provide concrete recommendations with evidence\n```\n\n**`/speckit-checklist`**\n```\n- [ ] Read feature requirements from spec.md\n- [ ] Generate custom verification checklist\n- [ ] Output checklist in markdown format\n- [ ] Verify checklist completeness\n```\n\n## Workflow Phase Tracking\n\n### Phase States\n\n1. **Not Started**: Prerequisites not yet validated\n2. **In Progress**: Command executing, artifacts being created\n3. **Blocked**: Waiting for user input or error resolution\n4. **Completed**: Artifacts created, verification passed\n5. **Failed**: Unrecoverable error, manual intervention needed\n\n### Phase Transitions\n\n```\nNot Started → In Progress: When prerequisites validated\nIn Progress → Blocked: When user input or clarification needed\nIn Progress → Failed: When unrecoverable error occurs\nIn Progress → Completed: When all exit criteria met\nBlocked → In Progress: When blocker resolved\n```\n\n### Status Reporting\n\nAfter each phase transition, report:\n- Current phase and status\n- Artifacts created/modified\n- Outstanding blockers (if any)\n- Next steps\n\n## Completion Verification Patterns\n\n### Specification Phase Verification\n\n- [ ] spec.md exists and is valid markdown\n- [ ] All required frontmatter fields present\n- [ ] All template sections completed\n- [ ] No placeholder text remains\n- [ ] Acceptance criteria are testable\n\n### Planning Phase Verification\n\n- [ ] plan.md exists and follows template\n- [ ] Design decisions documented with rationale\n- [ ] Architecture diagrams/descriptions present\n- [ ] Technical approach is clear\n- [ ] Risks and mitigations identified\n\n### Task Generation Verification\n\n- [ ] tasks.md exists with concrete tasks\n- [ ] Tasks are dependency-ordered\n- [ ] Each task has clear completion criteria\n- [ ] File paths and locations specified\n- [ ] Verification steps included\n\n### Implementation Phase Verification\n\n- [ ] All tasks in tasks.md completed\n- [ ] Code compiles/runs successfully\n- [ ] Tests pass (if applicable)\n- [ ] No unresolved TODOs or FIXMEs\n- [ ] Documentation updated\n\n### Cross-Artifact Verification\n\n- [ ] spec.md requirements match plan.md design\n- [ ] plan.md design matches tasks.md implementation\n- [ ] tasks.md tasks align with spec.md acceptance criteria\n- [ ] No conflicting information across artifacts\n- [ ] Version/date metadata is consistent\n\n## Progress Persistence\n\n### Session Continuity\n\n- Track progress in TodoWrite for current session\n- Save state to artifacts (spec.md, plan.md, tasks.md)\n- Use frontmatter metadata for phase tracking\n- Enable `/catchup` recovery across sessions\n\n### Recovery Patterns\n\n**After Session Interruption**:\n1. Read artifact frontmatter to determine last phase\n2. Check artifact completeness vs. expected state\n3. Resume from last verified checkpoint\n4. Re-validate prerequisites if needed\n\n**After Error**:\n1. Mark current phase as blocked\n2. Document error and attempted solutions\n3. Load systematic-debugging if needed\n4. Clear blocker, then resume progress\n\n## Metrics and Reporting\n\n### Track Per Session\n\n- Total workflow duration\n- Time per phase\n- Number of iterations (clarify, refactor)\n- Artifact sizes (lines, tokens)\n- User interactions required\n\n### Quality Metrics\n\n- Specification completeness score\n- Plan-spec alignment score\n- Task-plan alignment score\n- Cross-artifact consistency score\n\nFile v1.9.19:modules/writing-plans-extensions.md\n\n# Writing-Plans Extensions for Spec-kit\n\n## Overview\n\nThis document defines the extensions that spec-kit provides to enhance the `superpowers:writing-plans` skill with specification-driven artifact management, quality validation, and workflow integration.\n\n## Extension Categories\n\n### 1. Artifact Management Extensions\n\n#### Artifact Lifecycle Management\n```python\nclass ArtifactManager:\n def track_artifact_lifecycle(self, artifact_path: str) -> ArtifactStatus\n def validate_artifact_consistency(self, artifacts: List[str]) -> ConsistencyReport\n def generate_artifact_summary(self, phase: str) -> ArtifactSummary\n def detect_artifact_changes(self, since_timestamp: datetime) -> ChangeReport\n```\n\n#### Specification-Driven Artifact Generation\n- **Templates**: Use spec-kit templates for consistent artifact structure\n- **Cross-References**: Maintain bidirectional links between artifacts\n- **Version Control**: Track artifact versions and changes\n- **Quality Gates**: Apply spec-kit quality validation to all artifacts\n\n#### Artifact Types Managed\n1. **spec.md** - Feature specifications with user stories\n2. **plan.md** - Implementation plans with tech decisions\n3. **data-model.md** - Entity relationships and validation\n4. **contracts/** - API specifications and schemas\n5. **research.md** - Technical decisions and rationale\n6. **tasks.md** - Dependency-ordered implementation tasks\n7. **checklists/** - Quality validation checklists\n\n### 2. Quality Validation Extensions\n\n#### Specification-Driven Quality Gates\n```python\nclass QualityGateValidator:\n def validate_specification_completeness(self, spec_path: str) -> SpecQualityReport\n def validate_plan_consistency(self, plan_path: str, spec_path: str) -> ConsistencyReport\n def validate_task_completeness(self, tasks_path: str, plan_path: str) -> TaskQualityReport\n def validate_cross_artifact_alignment(self, artifacts: Dict[str, str]) -> AlignmentReport\n```\n\n#### Quality Criteria\n- **Specification Quality**: No implementation details, measurable success criteria\n- **Plan Consistency**: Tech decisions align with specifications\n- **Task Completeness**: All requirements have corresponding tasks\n- **Cross-Artifact Alignment**: No contradictions between artifacts\n\n#### Validation Reports\n```json\n{\n \"validation_timestamp\": \"2025-12-08T13:45:00Z\",\n \"overall_status\": \"pass\",\n \"artifact_validations\": {\n \"spec.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"completeness_score\": 0.95\n },\n \"plan.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"consistency_score\": 0.98\n }\n },\n \"cross_artifact_issues\": [],\n \"recommendations\": []\n}\n```\n\n### 3. Workflow Integration Extensions\n\n#### Phase Transition Management\n```python\nclass WorkflowOrchestrator:\n def transition_to_planning(self, spec_path: str) -> PlanningContext\n def transition_to_implementation(self, tasks_path: str) -> ImplementationContext\n def validate_phase_completion(self, phase: str, artifacts: List[str]) -> CompletionReport\n def generate_phase_summary(self, phase: str) -> PhaseSummary\n```\n\n#### Session Persistence\n- **State Management**: Maintain workflow state across sessions\n- **Progress Tracking**: Track completion of workflow phases\n- **Context Restoration**: Restore session state on restart\n- **Checkpoint System**: Create and restore checkpoints\n\n#### Skill Coordination\n- **Loading Order**: Optimize skill loading for maximum efficiency\n- **State Sharing**: Coordinate state between skills\n- **Conflict Resolution**: Handle conflicts between skill outputs\n- **Resource Management**: Optimize resource usage across skills\n\n### 4. Enhanced Planning Extensions\n\n#### Specification-Driven Task Generation\n```python\nclass SpecificationDrivenPlanner:\n def extract_user_stories(self, spec_path: str) -> List[UserStory]\n def map_entities_to_stories(self, data_model_path: str, stories: List[UserStory]) -> Mapping\n def generate_story_based_tasks(self, stories: List[UserStory], plan_path: str) -> List[Task]\n def create_dependency_graph(self, tasks: List[Task]) -> DependencyGraph\n```\n\n#### User Story Organization\n- **Story-Based Phases**: Organize tasks by user story\n- **Independent Testing**: Create testable story increments\n- **MVP Identification**: Identify minimum viable product scope\n- **Parallel Execution**: Identify parallelizable tasks within stories\n\n#### Enhanced Task Features\n- **Strict Formatting**: Enforce spec-kit task formatting standards\n- **File Path Precision**: Include exact file paths for all tasks\n- **Dependency Clarity**: Explicit dependency specification\n- **Parallel Markers**: Clear identification of parallelizable tasks\n\n### 5. Traceability Extensions\n\n#### Requirement Traceability Matrix\n```python\nclass TraceabilityManager:\n def create_requirement_traceability(self, spec_path: str, tasks_path: str) -> TraceabilityMatrix\n def validate_implementation_coverage(self, spec_path: str, implementation_path: str) -> CoverageReport\n def generate_impact_analysis(self, requirement_change: str) -> ImpactReport\n```\n\n#### Traceability Features\n- **Bidirectional Links**: Links from requirements to tasks and vice versa\n- **Change Impact**: Analyze impact of requirement changes\n- **Coverage Analysis**: Verify all requirements are implemented\n- **Validation Mapping**: Map tests back to requirements\n\n#### Traceability Reports\n```markdown\n# Requirement Traceability Matrix\n\n| Requirement ID | User Story | Tasks | Test Cases | Status |\n|---------------|------------|-------|------------|--------|\n| REQ-001 | US1 | T001, T002, T003 | TC-001, TC-002 | Implemented |\n| REQ-002 | US2 | T004, T005 | TC-003 | In Progress |\n```\n\n### 6. Template Integration Extensions\n\n#### Template Enhancement\n- **Writing-Plans Integration**: Enhance spec-kit templates with writing-plans methodology\n- **Dynamic Content**: Generate template content based on context\n- **Validation Rules**: Embed validation rules in templates\n- **Best Practices**: Include writing-plans best practices in templates\n\n#### Custom Template Features\n```python\nclass TemplateEnhancer:\n def enhance_plan_template(self, base_template: str, writing_plans_context: dict) -> str\n def generate_contextual_content(self, template_section: str, context: dict) -> str\n def apply_best_practices(self, content: str, domain: str) -> str\n def validate_template_output(self, generated_content: str) -> ValidationReport\n```\n\n## Integration Benefits\n\n### For Writing-Plans Skill\n1. **Specification Context**: Access to detailed specifications for better planning\n2. **Quality Assurance**: Built-in validation and quality gates\n3. **Artifact Management**: Automatic artifact generation and tracking\n4. **Workflow Integration**: smooth integration into spec-kit workflow\n\n### For Spec-kit Plugin\n1. **Enhanced Planning**: Access to writing-plans' detailed methodology\n2. **Better Task Generation**: More detailed and accurate task breakdown\n3. **Improved Quality**: Better validation and consistency checking\n4. **Session Management**: Enhanced session persistence and coordination\n\n## Usage Examples\n\n### Enhanced Planning Session\n```bash\n# Start enhanced session\n/speckit-startup.wrapped\n\n# Generate specification with writing-plans refinement\n/speckit-specify \"Add user authentication system\"\n\n# Create enhanced plan with writing-plans methodology\n/speckit-plan.wrapped\n\n# Generate detailed tasks with specification-driven organization\n/speckit-tasks.wrapped\n```\n\n### Quality Validation\n```python\n# Run detailed quality validation\nquality_report = validator.validate_cross_artifact_alignment({\n 'spec.md': '/specs/1-user-auth/spec.md',\n 'plan.md': '/specs/1-user-auth/plan.md',\n 'tasks.md': '/specs/1-user-auth/tasks.md'\n})\n\nprint(f\"Overall quality: {quality_report.overall_status}\")\nprint(f\"Issues found: {len(quality_report.cross_artifact_issues)}\")\n```\n\n## Configuration\n\n### Extension Activation\n```yaml\n# .specify/config/extensions.yml\nwriting_plans_extensions:\n enabled: true\n artifact_management: true\n quality_validation: true\n workflow_integration: true\n traceability: true\n template_enhancement: true\n```\n\n### Quality Gate Configuration\n```yaml\nquality_gates:\n specification:\n completeness_threshold: 0.9\n max_clarifications: 3\n success_criteria_required: true\n\n planning:\n consistency_threshold: 0.85\n dependency_validation: true\n task_formatting: strict\n\n implementation:\n coverage_threshold: 0.95\n test_coverage: true\n quality_checks: automated\n```\n\nThis specification provides the foundation for integrating spec-kit's artifact management and quality validation capabilities with the superpowers:writing-plans skill, creating a detailed planning and execution system.\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nOrchestrates Spec Driven Development by coordinating spec, plan, and task skills.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to coordinate spec-driven feature work across specification, planning, task generation, implementation, and verification phases.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can read and update project-level spec artifacts, so incorrect guidance could affect planning or implementation documents.\n\nMitigation: Review generated or modified spec.md, plan.md, tasks.md, and checklist artifacts before using them for implementation.\n\nRisk: Generic planning and specification triggers may activate the skill during ordinary workflow requests.\n\nMitigation: Confirm the intended speckit workflow before relying on its coordination guidance, or narrow activation triggers where the agent environment supports it.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-spec-kit-speckit-orchestrator)\n- [Spec-kit plugin homepage](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit)\n- [Artifact structure](modules/artifact-structure.md)\n- [Command-skill matrix](modules/command-skill-matrix.md)\n- [Progress tracking](modules/progress-tracking.md)\n- [Writing-plans extensions](modules/writing-plans-extensions.md)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Shell commands, Configuration]\n\n**Output Format:** [Markdown guidance with task lists and command-oriented workflow steps]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May read and update spec-kit artifacts such as spec.md, plan.md, tasks.md, and checklists.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release evidence; artifact frontmatter lists 1.9.8)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.17: 7 files, 13554 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5698b), modules/writing-plans-extensions.md (8735b), skill-card.md (2361b), SKILL.md (4533b), _meta.json (152b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: speckit-orchestrator\ndescription: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\nversion: 1.9.8\ntriggers:\n - speckit\n - workflow\n - orchestration\n - planning\n - specification\n - running the full speckit workflow from spec to implementation\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.superpowers:brainstorming\", \"night-market.superpowers:writing-plans\", \"night-market.superpowers:executing-plans\"]}}}\nsource: claude-night-market\nsource_plugin: spec-kit\n---\n\n> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Persistent Presence Lens](#persistent-presence-lens)\n- [When to Use](#when-to-use)\n- [Core Workflow](#core-workflow)\n- [Session Initialization](#session-initialization)\n- [Command-Skill Matrix](#command-skill-matrix)\n- [Progress Tracking Items](#progress-tracking-items)\n- [Exit Criteria](#exit-criteria)\n- [Related Skills](#related-skills)\n\n\n# Speckit Orchestrator\n\n## Overview\n\nCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.\n\n## Persistent Presence Lens\n\nTreat SDD as a minimal, testable \"self-modeling\" loop:\n\n- **World model**: repo + speckit artifacts (`spec.md`, `plan.md`, `tasks.md`)\n- **Agent model**: loaded skills/plugins + constraints (especially `.specify/memory/constitution.md`) + progress state\n\nThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (`tasks.md`) and a skill library (reusable plugin skills and superpowers methodology skills).\n\n## When To Use\n\n- Starting any `/speckit-*` command.\n- Coordinating multi-phase development workflows.\n- Tracking progress across specification, planning, and implementation.\n- Ensuring skill dependencies are loaded.\n\n## When NOT To Use\n\n- Single-phase work (just specify, or just plan)\n- Non-spec-driven projects\n\n## Core Workflow\n\n### Session Initialization\n\n1. **Verify Repository Context**\n - Confirm working directory is a speckit-enabled project.\n - Check for `.specify/` directory structure.\n - Validate required scripts exist.\n\n2. **Load Persistent State (\"presence\")**\n - Read `.specify/memory/constitution.md` for constraints/principles.\n - Load current `spec.md` / `plan.md` / `tasks.md` context if present.\n\n3. **Load Command Dependencies**\n - Match current command to required skills.\n - Load complementary superpowers skills.\n\n4. **Initialize Progress Tracking**\n - Create TodoWrite items for workflow phases.\n - Track completion status.\n\n### Command-Skill Matrix\n\nQuick reference for command-to-skill mappings:\n\n| Command | Primary Skill | Complementary Skills |\n|---------|--------------|---------------------|\n| `/speckit-specify` | spec-writing | brainstorming |\n| `/speckit-clarify` | spec-writing | brainstorming |\n| `/speckit-plan` | task-planning | writing-plans |\n| `/speckit-tasks` | task-planning | executing-plans |\n| `/speckit-implement` | - | executing-plans, systematic-debugging |\n| `/speckit-analyze` | - | systematic-debugging, verification |\n| `/speckit-checklist` | - | verification-before-completion |\n\n**For detailed patterns**: See `modules/command-skill-matrix.md` for complete mappings and loading rules.\n\nSee `modules/writing-plans-extensions.md` for plan authoring patterns.\n\n### Progress Tracking Items\n\nFor each workflow session, track:\n- [ ] Repository context verified.\n- [ ] Prerequisites validated.\n- [ ] Command-specific skills loaded.\n- [ ] Artifacts created/updated.\n- [ ] Verification completed.\n\n**For detailed patterns**: See `modules/progress-tracking.md` for TodoWrite patterns and metrics.\n\n## Exit Criteria\n\n- Active command completed successfully.\n- All required artifacts exist and are valid.\n- Progress tracking reflects current state.\n- No unresolved blockers.\n\n## Related Skills\n\n- `spec-writing`: Specification creation and refinement.\n- `task-planning`: Task generation and planning.\n- `superpowers:brainstorming`: Idea refinement.\n- `superpowers:writing-plans`: Implementation planning.\n- `superpowers:executing-plans`: Task execution.\n\nFile v1.9.17:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-spec-kit-speckit-orchestrator\",\n \"version\": \"1.9.17\",\n \"publishedAt\": 1785390181385\n}\n\nFile v1.9.17:modules/artifact-structure.md\n\n---\nname: artifact-structure\ndescription: Documentation of spec-kit artifact structure, purposes, and organization\ncategory: reference\ntags: [artifacts, structure, organization, documentation]\ndependencies: [speckit-orchestrator]\ncomplexity: beginner\nestimated_tokens: 800\n---\n\n# Spec-Kit Artifact Structure\n\n## Overview\n\nSpec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.\n\n## Directory Structure\n\n```\nproject-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/\n```\n\n> **Note: Claude Code Plan Mode Namespace**\n>\n> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the\n> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.\n> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid\n> collision. When searching for scope artifacts:\n> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)\n> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)\n>\n> The two systems are complementary: Claude Plan Mode is for exploratory planning,\n> while spec-kit plans are structured implementation blueprints.\n\n## Core Artifacts\n\n### spec.md - Feature Specification\n\n**Purpose**: Define WHAT users need and WHY, without implementation details.\n\n**Audience**: Business stakeholders, product managers, non-technical reviewers.\n\n**Structure**:\n```markdown\n# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Technology-agnostic metrics\n- User-facing goals\n\n## Success Criteria (Optional)\n- Performance expectations\n- Security considerations\n- Accessibility needs\n\n## Edge Cases (Optional)\n- Boundary conditions\n- Error scenarios\n- Fallback behaviors\n\n## Dependencies & Assumptions (Optional)\n- External dependencies\n- Documented assumptions\n```\n\n**Key Principles**:\n- No technology choices (no \"React\", \"PostgreSQL\", \"REST API\")\n- Focus on user value, not system internals\n- Measurable, testable requirements\n- Maximum 3 [NEEDS CLARIFICATION] markers\n\n### plan.md - Implementation Plan\n\n**Purpose**: Define HOW to build the feature technically.\n\n**Audience**: Developers, technical leads, architects.\n\n**Structure**:\n```markdown\n# Implementation Plan: Feature Name\n\n## Technical Context\n- Tech stack decisions\n- Architecture choices\n- Libraries and frameworks\n\n## Constitution Check\n- Alignment with project principles\n- Gate evaluation\n\n## Phase 0: Research\n- Technical unknowns\n- Best practices research\n- Decision rationale\n\n## Phase 1: Design\n- Data model\n- API contracts\n- Integration points\n\n## Phase 2: Implementation\n- Component structure\n- Service layer\n- Infrastructure needs\n```\n\n**Key Principles**:\n- Technology-specific\n- Includes research and decisions\n- Maps to project constitution\n- Generates tasks.md\n\n### tasks.md - Implementation Tasks\n\n**Purpose**: Actionable, dependency-ordered tasks for implementation.\n\n**Audience**: Developers executing the feature.\n\n**Structure**:\n```markdown\n# Implementation Tasks: Feature Name\n\n## Overview\n- Total tasks\n- Parallelization opportunities\n- MVP scope\n\n## Dependencies\n- User story completion order\n- Blocking prerequisites\n\n## Phase 1: Setup\n- [ ] T001 Project initialization\n- [ ] T002 [P] Configure tooling\n\n## Phase 2: Foundational\n- [ ] T010 Shared infrastructure\n\n## Phase 3: User Story 1 (P1)\n- [ ] T020 [US1] Model creation\n- [ ] T021 [P] [US1] Service implementation\n- [ ] T022 [US1] Endpoint implementation\n\n## Phase 4: User Story 2 (P2)\n- [ ] T030 [US2] Feature implementation\n\n## Final Phase: Polish\n- [ ] T090 Cross-cutting concerns\n- [ ] T091 Documentation\n```\n\n**Task Format**:\n```\n- [ ] [TaskID] [P?] [Story?] Description with file path\n```\n\n**Key Principles**:\n- Organized by user story\n- Sequential task IDs\n- Clear parallelization markers [P]\n- Story labels [US1], [US2], etc.\n- Explicit file paths\n\n### checklists/ - Quality Validation\n\n**Purpose**: \"Unit tests for requirements\" - validate requirement quality.\n\n**Audience**: Spec authors, reviewers, QA.\n\n**Structure**: Multiple domain-specific checklists:\n- `requirements.md` - Overall spec quality\n- `ux.md` - UX requirements validation\n- `api.md` - API requirements validation\n- `security.md` - Security requirements validation\n- `performance.md` - Performance requirements validation\n\n**Checklist Item Format**:\n```markdown\n- [ ] CHK001 Are [requirements] defined for [scenario]? [Dimension, Reference]\n```\n\n**Key Principles**:\n- Test requirements quality, NOT implementation\n- Focus on completeness, clarity, consistency\n- ≥80% traceability to spec sections\n- Question format, not verification statements\n\n## Supporting Artifacts\n\n### research.md\nDocuments technical research, decisions, and alternatives considered during Phase 0.\n\n### data-model.md\nDefines entities, fields, relationships, validation rules, and state transitions.\n\n### quickstart.md\nTest scenarios and acceptance testing guides for the feature.\n\n### contracts/\nAPI contracts (OpenAPI, GraphQL schemas) generated from functional requirements.\n\n## Workflow Progression\n\n1. **Specify**: Create spec.md (user-focused, no tech)\n2. **Clarify**: Resolve [NEEDS CLARIFICATION] markers\n3. **Checklist**: Validate spec quality with requirements.md checklist\n4. **Plan**: Create plan.md (technical design)\n5. **Tasks**: Generate tasks.md (actionable implementation)\n6. **Implement**: Execute tasks, mark complete\n7. **Validate**: Domain-specific checklists (ux.md, api.md, etc.)\n\n## Artifact Relationships\n\n```\nspec.md (WHAT/WHY)\n ↓\nchecklists/requirements.md (validate spec)\n ↓\nplan.md (HOW)\n ↓\ntasks.md (DO)\n ↓\nchecklists/[domain].md (validate implementation requirements)\n```\n\n## Usage in Commands\n\n- `/speckit-specify` → Creates spec.md, checklists/requirements.md\n- `/speckit-clarify` → Resolves [NEEDS CLARIFICATION] in spec.md\n- `/speckit-plan` → Creates plan.md, research.md, data-model.md, contracts/\n- `/speckit-tasks` → Generates tasks.md from plan.md + spec.md\n- `/speckit-checklist` → Creates domain-specific checklists (ux.md, api.md, etc.)\n- `/speckit-implement` → Executes tasks.md\n- `/speckit-analyze` → Cross-artifact consistency validation\n\nFile v1.9.17:modules/command-skill-matrix.md\n\n# Command-Skill Matrix\n\n## Overview\n\nThe Command-Skill Matrix defines which skills are required for each speckit command, ensuring proper dependencies are loaded and coordinated throughout the workflow.\n\n## Complete Mapping\n\n### Specification Phase\n\n**`/speckit-specify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: At command start, before any specification work\n- **Purpose**: Create or refine feature specifications with collaborative ideation\n\n**`/speckit-clarify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: When specification needs refinement or has gaps\n- **Purpose**: Identify underspecified areas and encode clarifications\n\n**`/speckit-constitution`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: None required\n- **Loading Order**: spec-writing only\n- **When to Load**: Creating or updating project principles\n- **Purpose**: Establish project governance and design principles\n\n### Planning Phase\n\n**`/speckit-plan`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:writing-plans`\n- **Loading Order**: task-planning → writing-plans\n- **When to Load**: After specification is complete\n- **Purpose**: Generate detailed implementation design artifacts\n\n**`/speckit-tasks`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:executing-plans`\n- **Loading Order**: task-planning → executing-plans\n- **When to Load**: After planning artifacts exist\n- **Purpose**: Generate dependency-ordered implementation tasks\n\n### Implementation Phase\n\n**`/speckit-implement`**\n- **Primary Skill**: None (uses loaded plan)\n- **Complementary Skills**: `superpowers:executing-plans`, `superpowers:systematic-debugging`\n- **Loading Order**: executing-plans → systematic-debugging (on-demand)\n- **When to Load**: When executing tasks from tasks.md\n- **Purpose**: Execute implementation tasks with error handling\n\n### Verification Phase\n\n**`/speckit-analyze`**\n- **Primary Skill**: None (analysis only)\n- **Complementary Skills**: `superpowers:systematic-debugging`, `superpowers:verification-before-completion`\n- **Loading Order**: Load both at analysis start\n- **When to Load**: After task generation or implementation\n- **Purpose**: Cross-artifact consistency and quality analysis\n\n**`/speckit-checklist`**\n- **Primary Skill**: None (generation only)\n- **Complementary Skills**: `superpowers:verification-before-completion`\n- **Loading Order**: verification-before-completion only\n- **When to Load**: When generating feature-specific checklists\n- **Purpose**: Create custom verification checklists\n\n**`/speckit-startup`**\n- **Primary Skill**: None (bootstrap only)\n- **Complementary Skills**: None required\n- **Loading Order**: N/A\n- **When to Load**: Session initialization\n- **Purpose**: Bootstrap workflow and verify environment\n\n## Skill Loading Priorities\n\n### High Priority (Always Load First)\n1. `spec-writing` - For any specification work\n2. `task-planning` - For any planning work\n\n### Medium Priority (Load After Primary)\n3. `superpowers:brainstorming` - For ideation phases\n4. `superpowers:writing-plans` - For detailed planning\n5. `superpowers:executing-plans` - For implementation\n\n### Low Priority (Load On-Demand)\n6. `superpowers:systematic-debugging` - When errors occur\n7. `superpowers:verification-before-completion` - For final checks\n\n## Conditional Loading Rules\n\n- **Brainstorming**: Only load if specification is new or incomplete\n- **Systematic Debugging**: Only load if implementation encounters errors\n- **Verification**: Only load for analyze/checklist commands or before completion\n- **Writing Plans**: Only load if creating new implementation plans\n\n## Skill Interaction Patterns\n\n### Specification → Planning\n- Specification skills complete → task-planning loads\n- Hand off spec.md to planning phase\n\n### Planning → Implementation\n- Planning skills complete → executing-plans loads\n- Hand off tasks.md to implementation phase\n\n### Implementation → Verification\n- Implementation errors → systematic-debugging loads\n- Implementation complete → verification-before-completion loads\n\nFile v1.9.17:modules/progress-tracking.md\n\n# Progress Tracking\n\n## Overview\n\nDefines TodoWrite item patterns and progress tracking strategies for speckit workflows. validates consistent status reporting and verification throughout all workflow phases.\n\n## TodoWrite Item Patterns\n\n### Universal Workflow Items\n\nFor every speckit command session:\n\n```\n- [ ] Verify repository context and .specify/ structure\n- [ ] Validate prerequisites (scripts, dependencies, templates)\n- [ ] Load command-specific skills\n- [ ] Execute command workflow\n- [ ] Verify artifacts created/updated\n- [ ] Complete progress tracking\n```\n\n### Specification Phase Items\n\n**`/speckit-specify`**\n```\n- [ ] Load spec-writing and brainstorming skills\n- [ ] Analyze feature description and requirements\n- [ ] Generate/update spec.md with template\n- [ ] Verify spec.md contains all required sections\n- [ ] Validate frontmatter metadata\n```\n\n**`/speckit-clarify`**\n```\n- [ ] Read existing spec.md\n- [ ] Identify underspecified areas\n- [ ] Ask targeted clarification questions (max 5)\n- [ ] Encode answers back into spec.md\n- [ ] Verify improved specification completeness\n```\n\n**`/speckit-constitution`**\n```\n- [ ] Gather project principles (interactive or provided)\n- [ ] Create/update constitution.md\n- [ ] Sync dependent templates with constitution\n- [ ] Verify template consistency\n```\n\n### Planning Phase Items\n\n**`/speckit-plan`**\n```\n- [ ] Load task-planning and writing-plans skills\n- [ ] Read spec.md and constitution.md\n- [ ] Execute planning template workflow\n- [ ] Generate plan.md with design artifacts\n- [ ] Verify plan completeness and consistency\n```\n\n**`/speckit-tasks`**\n```\n- [ ] Read all available design artifacts (spec, plan, constitution)\n- [ ] Analyze dependencies and ordering constraints\n- [ ] Generate tasks.md with concrete tasks\n- [ ] Verify task ordering and completeness\n- [ ] Mark tasks ready for implementation\n```\n\n### Implementation Phase Items\n\n**`/speckit-implement`**\n```\n- [ ] Load executing-plans skill\n- [ ] Read and parse tasks.md\n- [ ] Execute tasks in dependency order\n- [ ] Track completion status per task\n- [ ] Handle errors with systematic-debugging\n- [ ] Verify all tasks completed successfully\n```\n\n### Verification Phase Items\n\n**`/speckit-analyze`**\n```\n- [ ] Read spec.md, plan.md, tasks.md\n- [ ] Check cross-artifact consistency\n- [ ] Identify quality issues\n- [ ] Generate analysis report\n- [ ] Provide concrete recommendations with evidence\n```\n\n**`/speckit-checklist`**\n```\n- [ ] Read feature requirements from spec.md\n- [ ] Generate custom verification checklist\n- [ ] Output checklist in markdown format\n- [ ] Verify checklist completeness\n```\n\n## Workflow Phase Tracking\n\n### Phase States\n\n1. **Not Started**: Prerequisites not yet validated\n2. **In Progress**: Command executing, artifacts being created\n3. **Blocked**: Waiting for user input or error resolution\n4. **Completed**: Artifacts created, verification passed\n5. **Failed**: Unrecoverable error, manual intervention needed\n\n### Phase Transitions\n\n```\nNot Started → In Progress: When prerequisites validated\nIn Progress → Blocked: When user input or clarification needed\nIn Progress → Failed: When unrecoverable error occurs\nIn Progress → Completed: When all exit criteria met\nBlocked → In Progress: When blocker resolved\n```\n\n### Status Reporting\n\nAfter each phase transition, report:\n- Current phase and status\n- Artifacts created/modified\n- Outstanding blockers (if any)\n- Next steps\n\n## Completion Verification Patterns\n\n### Specification Phase Verification\n\n- [ ] spec.md exists and is valid markdown\n- [ ] All required frontmatter fields present\n- [ ] All template sections completed\n- [ ] No placeholder text remains\n- [ ] Acceptance criteria are testable\n\n### Planning Phase Verification\n\n- [ ] plan.md exists and follows template\n- [ ] Design decisions documented with rationale\n- [ ] Architecture diagrams/descriptions present\n- [ ] Technical approach is clear\n- [ ] Risks and mitigations identified\n\n### Task Generation Verification\n\n- [ ] tasks.md exists with concrete tasks\n- [ ] Tasks are dependency-ordered\n- [ ] Each task has clear completion criteria\n- [ ] File paths and locations specified\n- [ ] Verification steps included\n\n### Implementation Phase Verification\n\n- [ ] All tasks in tasks.md completed\n- [ ] Code compiles/runs successfully\n- [ ] Tests pass (if applicable)\n- [ ] No unresolved TODOs or FIXMEs\n- [ ] Documentation updated\n\n### Cross-Artifact Verification\n\n- [ ] spec.md requirements match plan.md design\n- [ ] plan.md design matches tasks.md implementation\n- [ ] tasks.md tasks align with spec.md acceptance criteria\n- [ ] No conflicting information across artifacts\n- [ ] Version/date metadata is consistent\n\n## Progress Persistence\n\n### Session Continuity\n\n- Track progress in TodoWrite for current session\n- Save state to artifacts (spec.md, plan.md, tasks.md)\n- Use frontmatter metadata for phase tracking\n- Enable `/catchup` recovery across sessions\n\n### Recovery Patterns\n\n**After Session Interruption**:\n1. Read artifact frontmatter to determine last phase\n2. Check artifact completeness vs. expected state\n3. Resume from last verified checkpoint\n4. Re-validate prerequisites if needed\n\n**After Error**:\n1. Mark current phase as blocked\n2. Document error and attempted solutions\n3. Load systematic-debugging if needed\n4. Clear blocker, then resume progress\n\n## Metrics and Reporting\n\n### Track Per Session\n\n- Total workflow duration\n- Time per phase\n- Number of iterations (clarify, refactor)\n- Artifact sizes (lines, tokens)\n- User interactions required\n\n### Quality Metrics\n\n- Specification completeness score\n- Plan-spec alignment score\n- Task-plan alignment score\n- Cross-artifact consistency score\n\nFile v1.9.17:modules/writing-plans-extensions.md\n\n# Writing-Plans Extensions for Spec-kit\n\n## Overview\n\nThis document defines the extensions that spec-kit provides to enhance the `superpowers:writing-plans` skill with specification-driven artifact management, quality validation, and workflow integration.\n\n## Extension Categories\n\n### 1. Artifact Management Extensions\n\n#### Artifact Lifecycle Management\n```python\nclass ArtifactManager:\n def track_artifact_lifecycle(self, artifact_path: str) -> ArtifactStatus\n def validate_artifact_consistency(self, artifacts: List[str]) -> ConsistencyReport\n def generate_artifact_summary(self, phase: str) -> ArtifactSummary\n def detect_artifact_changes(self, since_timestamp: datetime) -> ChangeReport\n```\n\n#### Specification-Driven Artifact Generation\n- **Templates**: Use spec-kit templates for consistent artifact structure\n- **Cross-References**: Maintain bidirectional links between artifacts\n- **Version Control**: Track artifact versions and changes\n- **Quality Gates**: Apply spec-kit quality validation to all artifacts\n\n#### Artifact Types Managed\n1. **spec.md** - Feature specifications with user stories\n2. **plan.md** - Implementation plans with tech decisions\n3. **data-model.md** - Entity relationships and validation\n4. **contracts/** - API specifications and schemas\n5. **research.md** - Technical decisions and rationale\n6. **tasks.md** - Dependency-ordered implementation tasks\n7. **checklists/** - Quality validation checklists\n\n### 2. Quality Validation Extensions\n\n#### Specification-Driven Quality Gates\n```python\nclass QualityGateValidator:\n def validate_specification_completeness(self, spec_path: str) -> SpecQualityReport\n def validate_plan_consistency(self, plan_path: str, spec_path: str) -> ConsistencyReport\n def validate_task_completeness(self, tasks_path: str, plan_path: str) -> TaskQualityReport\n def validate_cross_artifact_alignment(self, artifacts: Dict[str, str]) -> AlignmentReport\n```\n\n#### Quality Criteria\n- **Specification Quality**: No implementation details, measurable success criteria\n- **Plan Consistency**: Tech decisions align with specifications\n- **Task Completeness**: All requirements have corresponding tasks\n- **Cross-Artifact Alignment**: No contradictions between artifacts\n\n#### Validation Reports\n```json\n{\n \"validation_timestamp\": \"2025-12-08T13:45:00Z\",\n \"overall_status\": \"pass\",\n \"artifact_validations\": {\n \"spec.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"completeness_score\": 0.95\n },\n \"plan.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"consistency_score\": 0.98\n }\n },\n \"cross_artifact_issues\": [],\n \"recommendations\": []\n}\n```\n\n### 3. Workflow Integration Extensions\n\n#### Phase Transition Management\n```python\nclass WorkflowOrchestrator:\n def transition_to_planning(self, spec_path: str) -> PlanningContext\n def transition_to_implementation(self, tasks_path: str) -> ImplementationContext\n def validate_phase_completion(self, phase: str, artifacts: List[str]) -> CompletionReport\n def generate_phase_summary(self, phase: str) -> PhaseSummary\n```\n\n#### Session Persistence\n- **State Management**: Maintain workflow state across sessions\n- **Progress Tracking**: Track completion of workflow phases\n- **Context Restoration**: Restore session state on restart\n- **Checkpoint System**: Create and restore checkpoints\n\n#### Skill Coordination\n- **Loading Order**: Optimize skill loading for maximum efficiency\n- **State Sharing**: Coordinate state between skills\n- **Conflict Resolution**: Handle conflicts between skill outputs\n- **Resource Management**: Optimize resource usage across skills\n\n### 4. Enhanced Planning Extensions\n\n#### Specification-Driven Task Generation\n```python\nclass SpecificationDrivenPlanner:\n def extract_user_stories(self, spec_path: str) -> List[UserStory]\n def map_entities_to_stories(self, data_model_path: str, stories: List[UserStory]) -> Mapping\n def generate_story_based_tasks(self, stories: List[UserStory], plan_path: str) -> List[Task]\n def create_dependency_graph(self, tasks: List[Task]) -> DependencyGraph\n```\n\n#### User Story Organization\n- **Story-Based Phases**: Organize tasks by user story\n- **Independent Testing**: Create testable story increments\n- **MVP Identification**: Identify minimum viable product scope\n- **Parallel Execution**: Identify parallelizable tasks within stories\n\n#### Enhanced Task Features\n- **Strict Formatting**: Enforce spec-kit task formatting standards\n- **File Path Precision**: Include exact file paths for all tasks\n- **Dependency Clarity**: Explicit dependency specification\n- **Parallel Markers**: Clear identification of parallelizable tasks\n\n### 5. Traceability Extensions\n\n#### Requirement Traceability Matrix\n```python\nclass TraceabilityManager:\n def create_requirement_traceability(self, spec_path: str, tasks_path: str) -> TraceabilityMatrix\n def validate_implementation_coverage(self, spec_path: str, implementation_path: str) -> CoverageReport\n def generate_impact_analysis(self, requirement_change: str) -> ImpactReport\n```\n\n#### Traceability Features\n- **Bidirectional Links**: Links from requirements to tasks and vice versa\n- **Change Impact**: Analyze impact of requirement changes\n- **Coverage Analysis**: Verify all requirements are implemented\n- **Validation Mapping**: Map tests back to requirements\n\n#### Traceability Reports\n```markdown\n# Requirement Traceability Matrix\n\n| Requirement ID | User Story | Tasks | Test Cases | Status |\n|---------------|------------|-------|------------|--------|\n| REQ-001 | US1 | T001, T002, T003 | TC-001, TC-002 | Implemented |\n| REQ-002 | US2 | T004, T005 | TC-003 | In Progress |\n```\n\n### 6. Template Integration Extensions\n\n#### Template Enhancement\n- **Writing-Plans Integration**: Enhance spec-kit templates with writing-plans methodology\n- **Dynamic Content**: Generate template content based on context\n- **Validation Rules**: Embed validation rules in templates\n- **Best Practices**: Include writing-plans best practices in templates\n\n#### Custom Template Features\n```python\nclass TemplateEnhancer:\n def enhance_plan_template(self, base_template: str, writing_plans_context: dict) -> str\n def generate_contextual_content(self, template_section: str, context: dict) -> str\n def apply_best_practices(self, content: str, domain: str) -> str\n def validate_template_output(self, generated_content: str) -> ValidationReport\n```\n\n## Integration Benefits\n\n### For Writing-Plans Skill\n1. **Specification Context**: Access to detailed specifications for better planning\n2. **Quality Assurance**: Built-in validation and quality gates\n3. **Artifact Management**: Automatic artifact generation and tracking\n4. **Workflow Integration**: smooth integration into spec-kit workflow\n\n### For Spec-kit Plugin\n1. **Enhanced Planning**: Access to writing-plans' detailed methodology\n2. **Better Task Generation**: More detailed and accurate task breakdown\n3. **Improved Quality**: Better validation and consistency checking\n4. **Session Management**: Enhanced session persistence and coordination\n\n## Usage Examples\n\n### Enhanced Planning Session\n```bash\n# Start enhanced session\n/speckit-startup.wrapped\n\n# Generate specification with writing-plans refinement\n/speckit-specify \"Add user authentication system\"\n\n# Create enhanced plan with writing-plans methodology\n/speckit-plan.wrapped\n\n# Generate detailed tasks with specification-driven organization\n/speckit-tasks.wrapped\n```\n\n### Quality Validation\n```python\n# Run detailed quality validation\nquality_report = validator.validate_cross_artifact_alignment({\n 'spec.md': '/specs/1-user-auth/spec.md',\n 'plan.md': '/specs/1-user-auth/plan.md',\n 'tasks.md': '/specs/1-user-auth/tasks.md'\n})\n\nprint(f\"Overall quality: {quality_report.overall_status}\")\nprint(f\"Issues found: {len(quality_report.cross_artifact_issues)}\")\n```\n\n## Configuration\n\n### Extension Activation\n```yaml\n# .specify/config/extensions.yml\nwriting_plans_extensions:\n enabled: true\n artifact_management: true\n quality_validation: true\n workflow_integration: true\n traceability: true\n template_enhancement: true\n```\n\n### Quality Gate Configuration\n```yaml\nquality_gates:\n specification:\n completeness_threshold: 0.9\n max_clarifications: 3\n success_criteria_required: true\n\n planning:\n consistency_threshold: 0.85\n dependency_validation: true\n task_formatting: strict\n\n implementation:\n coverage_threshold: 0.95\n test_coverage: true\n quality_checks: automated\n```\n\nThis specification provides the foundation for integrating spec-kit's artifact management and quality validation capabilities with the superpowers:writing-plans skill, creating a detailed planning and execution system.\n\nFile v1.9.17:skill-card.md\n\n## Description:
\nOrchestrates Spec Driven Development by coordinating spec, plan, and task skills.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to coordinate speckit-style specification, planning, task generation, implementation, and verification workflows across spec.md, plan.md, and tasks.md artifacts.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad triggers may activate the skill during ordinary planning discussions.
\nMitigation: Invoke it explicitly for speckit work and confirm the intended workflow phase before applying generated guidance or artifact changes.
\nRisk: Incorrectly coordinated spec, plan, task, or checklist artifacts can mislead later implementation work.
\nMitigation: Review generated artifacts for consistency with the repository constitution and verify cross-artifact alignment before implementation.
\n\n\n## Reference(s):
\n- [ClawHub skill listing](https://clawhub.ai/athola/skills/nm-spec-kit-speckit-orchestrator)
\n- [Spec-kit plugin homepage](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit)
\n- [Artifact structure](modules/artifact-structure.md)
\n- [Command-skill matrix](modules/command-skill-matrix.md)
\n- [Progress tracking](modules/progress-tracking.md)
\n- [Writing-plans extensions](modules/writing-plans-extensions.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown guidance with checklists, command mappings, progress items, and inline command examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Coordinates spec.md, plan.md, tasks.md, checklists, and related spec-kit artifacts.]
\n\n## Skill Version(s):
\n1.9.17 (source: server release metadata; artifact frontmatter reports 1.9.8)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.16: 7 files, 13429 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5698b), modules/writing-plans-extensions.md (8735b), skill-card.md (2032b), SKILL.md (4533b), _meta.json (152b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: speckit-orchestrator\ndescription: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\nversion: 1.9.8\ntriggers:\n - speckit\n - workflow\n - orchestration\n - planning\n - specification\n - running the full speckit workflow from spec to implementation\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.superpowers:brainstorming\", \"night-market.superpowers:writing-plans\", \"night-market.superpowers:executing-plans\"]}}}\nsource: claude-night-market\nsource_plugin: spec-kit\n---\n\n> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Persistent Presence Lens](#persistent-presence-lens)\n- [When to Use](#when-to-use)\n- [Core Workflow](#core-workflow)\n- [Session Initialization](#session-initialization)\n- [Command-Skill Matrix](#command-skill-matrix)\n- [Progress Tracking Items](#progress-tracking-items)\n- [Exit Criteria](#exit-criteria)\n- [Related Skills](#related-skills)\n\n\n# Speckit Orchestrator\n\n## Overview\n\nCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.\n\n## Persistent Presence Lens\n\nTreat SDD as a minimal, testable \"self-modeling\" loop:\n\n- **World model**: repo + speckit artifacts (`spec.md`, `plan.md`, `tasks.md`)\n- **Agent model**: loaded skills/plugins + constraints (especially `.specify/memory/constitution.md`) + progress state\n\nThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (`tasks.md`) and a skill library (reusable plugin skills and superpowers methodology skills).\n\n## When To Use\n\n- Starting any `/speckit-*` command.\n- Coordinating multi-phase development workflows.\n- Tracking progress across specification, planning, and implementation.\n- Ensuring skill dependencies are loaded.\n\n## When NOT To Use\n\n- Single-phase work (just specify, or just plan)\n- Non-spec-driven projects\n\n## Core Workflow\n\n### Session Initialization\n\n1. **Verify Repository Context**\n - Confirm working directory is a speckit-enabled project.\n - Check for `.specify/` directory structure.\n - Validate required scripts exist.\n\n2. **Load Persistent State (\"presence\")**\n - Read `.specify/memory/constitution.md` for constraints/principles.\n - Load current `spec.md` / `plan.md` / `tasks.md` context if present.\n\n3. **Load Command Dependencies**\n - Match current command to required skills.\n - Load complementary superpowers skills.\n\n4. **Initialize Progress Tracking**\n - Create TodoWrite items for workflow phases.\n - Track completion status.\n\n### Command-Skill Matrix\n\nQuick reference for command-to-skill mappings:\n\n| Command | Primary Skill | Complementary Skills |\n|---------|--------------|---------------------|\n| `/speckit-specify` | spec-writing | brainstorming |\n| `/speckit-clarify` | spec-writing | brainstorming |\n| `/speckit-plan` | task-planning | writing-plans |\n| `/speckit-tasks` | task-planning | executing-plans |\n| `/speckit-implement` | - | executing-plans, systematic-debugging |\n| `/speckit-analyze` | - | systematic-debugging, verification |\n| `/speckit-checklist` | - | verification-before-completion |\n\n**For detailed patterns**: See `modules/command-skill-matrix.md` for complete mappings and loading rules.\n\nSee `modules/writing-plans-extensions.md` for plan authoring patterns.\n\n### Progress Tracking Items\n\nFor each workflow session, track:\n- [ ] Repository context verified.\n- [ ] Prerequisites validated.\n- [ ] Command-specific skills loaded.\n- [ ] Artifacts created/updated.\n- [ ] Verification completed.\n\n**For detailed patterns**: See `modules/progress-tracking.md` for TodoWrite patterns and metrics.\n\n## Exit Criteria\n\n- Active command completed successfully.\n- All required artifacts exist and are valid.\n- Progress tracking reflects current state.\n- No unresolved blockers.\n\n## Related Skills\n\n- `spec-writing`: Specification creation and refinement.\n- `task-planning`: Task generation and planning.\n- `superpowers:brainstorming`: Idea refinement.\n- `superpowers:writing-plans`: Implementation planning.\n- `superpowers:executing-plans`: Task execution.\n\nFile v1.9.16:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-spec-kit-speckit-orchestrator\",\n \"version\": \"1.9.16\",\n \"publishedAt\": 1784059191620\n}\n\nFile v1.9.16:modules/artifact-structure.md\n\n---\nname: artifact-structure\ndescription: Documentation of spec-kit artifact structure, purposes, and organization\ncategory: reference\ntags: [artifacts, structure, organization, documentation]\ndependencies: [speckit-orchestrator]\ncomplexity: beginner\nestimated_tokens: 800\n---\n\n# Spec-Kit Artifact Structure\n\n## Overview\n\nSpec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.\n\n## Directory Structure\n\n```\nproject-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/\n```\n\n> **Note: Claude Code Plan Mode Namespace**\n>\n> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the\n> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.\n> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid\n> collision. When searching for scope artifacts:\n> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)\n> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)\n>\n> The two systems are complementary: Claude Plan Mode is for exploratory planning,\n> while spec-kit plans are structured implementation blueprints.\n\n## Core Artifacts\n\n### spec.md - Feature Specification\n\n**Purpose**: Define WHAT users need and WHY, without implementation details.\n\n**Audience**: Business stakeholders, product managers, non-technical reviewers.\n\n**Structure**:\n```markdown\n# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Technology-agnostic metrics\n- User-facing goals\n\n## Success Criteria (Optional)\n- Performance expectations\n- Security considerations\n- Accessibility needs\n\n## Edge Cases (Optional)\n- Boundary conditions\n- Error scenarios\n- Fallback behaviors\n\n## Dependencies & Assumptions (Optional)\n- External dependencies\n- Documented assumptions\n```\n\n**Key Principles**:\n- No technology choices (no \"React\", \"PostgreSQL\", \"REST API\")\n- Focus on user value, not system internals\n- Measurable, testable requirements\n- Maximum 3 [NEEDS CLARIFICATION] markers\n\n### plan.md - Implementation Plan\n\n**Purpose**: Define HOW to build the feature technically.\n\n**Audience**: Developers, technical leads, architects.\n\n**Structure**:\n```markdown\n# Implementation Plan: Feature Name\n\n## Technical Context\n- Tech stack decisions\n- Architecture choices\n- Libraries and frameworks\n\n## Constitution Check\n- Alignment with project principles\n- Gate evaluation\n\n## Phase 0: Research\n- Technical unknowns\n- Best practices research\n- Decision rationale\n\n## Phase 1: Design\n- Data model\n- API contracts\n- Integration points\n\n## Phase 2: Implementation\n- Component structure\n- Service layer\n- Infrastructure needs\n```\n\n**Key Principles**:\n- Technology-specific\n- Includes research and decisions\n- Maps to project constitution\n- Generates tasks.md\n\n### tasks.md - Implementation Tasks\n\n**Purpose**: Actionable, dependency-ordered tasks for implementation.\n\n**Audience**: Developers executing the feature.\n\n**Structure**:\n```markdown\n# Implementation Tasks: Feature Name\n\n## Overview\n- Total tasks\n- Parallelization opportunities\n- MVP scope\n\n## Dependencies\n- User story completion order\n- Blocking prerequisites\n\n## Phase 1: Setup\n- [ ] T001 Project initialization\n- [ ] T002 [P] Configure tooling\n\n## Phase 2: Foundational\n- [ ] T010 Shared infrastructure\n\n## Phase 3: User Story 1 (P1)\n- [ ] T020 [US1] Model creation\n- [ ] T021 [P] [US1] Service implementation\n- [ ] T022 [US1] Endpoint implementation\n\n## Phase 4: User Story 2 (P2)\n- [ ] T030 [US2] Feature implementation\n\n## Final Phase: Polish\n- [ ] T090 Cross-cutting concerns\n- [ ] T091 Documentation\n```\n\n**Task Format**:\n```\n- [ ] [TaskID] [P?] [Story?] Description with file path\n```\n\n**Key Principles**:\n- Organized by user story\n- Sequential task IDs\n- Clear parallelization markers [P]\n- Story labels [US1], [US2], etc.\n- Explicit file paths\n\n### checklists/ - Quality Validation\n\n**Purpose**: \"Unit tests for requirements\" - validate requirement quality.\n\n**Audience**: Spec authors, reviewers, QA.\n\n**Structure**: Multiple domain-specific checklists:\n- `requirements.md` - Overall spec quality\n- `ux.md` - UX requirements validation\n- `api.md` - API requirements validation\n- `security.md` - Security requirements validation\n- `performance.md` - Performance requirements validation\n\n**Checklist Item Format**:\n```markdown\n- [ ] CHK001 Are [requirements] defined for [scenario]? [Dimension, Reference]\n```\n\n**Key Principles**:\n- Test requirements quality, NOT implementation\n- Focus on completeness, clarity, consistency\n- ≥80% traceability to spec sections\n- Question format, not verification statements\n\n## Supporting Artifacts\n\n### research.md\nDocuments technical research, decisions, and alternatives considered during Phase 0.\n\n### data-model.md\nDefines entities, fields, relationships, validation rules, and state transitions.\n\n### quickstart.md\nTest scenarios and acceptance testing guides for the feature.\n\n### contracts/\nAPI contracts (OpenAPI, GraphQL schemas) generated from functional requirements.\n\n## Workflow Progression\n\n1. **Specify**: Create spec.md (user-focused, no tech)\n2. **Clarify**: Resolve [NEEDS CLARIFICATION] markers\n3. **Checklist**: Validate spec quality with requirements.md checklist\n4. **Plan**: Create plan.md (technical design)\n5. **Tasks**: Generate tasks.md (actionable implementation)\n6. **Implement**: Execute tasks, mark complete\n7. **Validate**: Domain-specific checklists (ux.md, api.md, etc.)\n\n## Artifact Relationships\n\n```\nspec.md (WHAT/WHY)\n ↓\nchecklists/requirements.md (validate spec)\n ↓\nplan.md (HOW)\n ↓\ntasks.md (DO)\n ↓\nchecklists/[domain].md (validate implementation requirements)\n```\n\n## Usage in Commands\n\n- `/speckit-specify` → Creates spec.md, checklists/requirements.md\n- `/speckit-clarify` → Resolves [NEEDS CLARIFICATION] in spec.md\n- `/speckit-plan` → Creates plan.md, research.md, data-model.md, contracts/\n- `/speckit-tasks` → Generates tasks.md from plan.md + spec.md\n- `/speckit-checklist` → Creates domain-specific checklists (ux.md, api.md, etc.)\n- `/speckit-implement` → Executes tasks.md\n- `/speckit-analyze` → Cross-artifact consistency validation\n\nFile v1.9.16:modules/command-skill-matrix.md\n\n# Command-Skill Matrix\n\n## Overview\n\nThe Command-Skill Matrix defines which skills are required for each speckit command, ensuring proper dependencies are loaded and coordinated throughout the workflow.\n\n## Complete Mapping\n\n### Specification Phase\n\n**`/speckit-specify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: At command start, before any specification work\n- **Purpose**: Create or refine feature specifications with collaborative ideation\n\n**`/speckit-clarify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: When specification needs refinement or has gaps\n- **Purpose**: Identify underspecified areas and encode clarifications\n\n**`/speckit-constitution`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: None required\n- **Loading Order**: spec-writing only\n- **When to Load**: Creating or updating project principles\n- **Purpose**: Establish project governance and design principles\n\n### Planning Phase\n\n**`/speckit-plan`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:writing-plans`\n- **Loading Order**: task-planning → writing-plans\n- **When to Load**: After specification is complete\n- **Purpose**: Generate detailed implementation design artifacts\n\n**`/speckit-tasks`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:executing-plans`\n- **Loading Order**: task-planning → executing-plans\n- **When to Load**: After planning artifacts exist\n- **Purpose**: Generate dependency-ordered implementation tasks\n\n### Implementation Phase\n\n**`/speckit-implement`**\n- **Primary Skill**: None (uses loaded plan)\n- **Complementary Skills**: `superpowers:executing-plans`, `superpowers:systematic-debugging`\n- **Loading Order**: executing-plans → systematic-debugging (on-demand)\n- **When to Load**: When executing tasks from tasks.md\n- **Purpose**: Execute implementation tasks with error handling\n\n### Verification Phase\n\n**`/speckit-analyze`**\n- **Primary Skill**: None (analysis only)\n- **Complementary Skills**: `superpowers:systematic-debugging`, `superpowers:verification-before-completion`\n- **Loading Order**: Load both at analysis start\n- **When to Load**: After task generation or implementation\n- **Purpose**: Cross-artifact consistency and quality analysis\n\n**`/speckit-checklist`**\n- **Primary Skill**: None (generation only)\n- **Complementary Skills**: `superpowers:verification-before-completion`\n- **Loading Order**: verification-before-completion only\n- **When to Load**: When generating feature-specific checklists\n- **Purpose**: Create custom verification checklists\n\n**`/speckit-startup`**\n- **Primary Skill**: None (bootstrap only)\n- **Complementary Skills**: None required\n- **Loading Order**: N/A\n- **When to Load**: Session initialization\n- **Purpose**: Bootstrap workflow and verify environment\n\n## Skill Loading Priorities\n\n### High Priority (Always Load First)\n1. `spec-writing` - For any specification work\n2. `task-planning` - For any planning work\n\n### Medium Priority (Load After Primary)\n3. `superpowers:brainstorming` - For ideation phases\n4. `superpowers:writing-plans` - For detailed planning\n5. `superpowers:executing-plans` - For implementation\n\n### Low Priority (Load On-Demand)\n6. `superpowers:systematic-debugging` - When errors occur\n7. `superpowers:verification-before-completion` - For final checks\n\n## Conditional Loading Rules\n\n- **Brainstorming**: Only load if specification is new or incomplete\n- **Systematic Debugging**: Only load if implementation encounters errors\n- **Verification**: Only load for analyze/checklist commands or before completion\n- **Writing Plans**: Only load if creating new implementation plans\n\n## Skill Interaction Patterns\n\n### Specification → Planning\n- Specification skills complete → task-planning loads\n- Hand off spec.md to planning phase\n\n### Planning → Implementation\n- Planning skills complete → executing-plans loads\n- Hand off tasks.md to implementation phase\n\n### Implementation → Verification\n- Implementation errors → systematic-debugging loads\n- Implementation complete → verification-before-completion loads\n\nFile v1.9.16:modules/progress-tracking.md\n\n# Progress Tracking\n\n## Overview\n\nDefines TodoWrite item patterns and progress tracking strategies for speckit workflows. validates consistent status reporting and verification throughout all workflow phases.\n\n## TodoWrite Item Patterns\n\n### Universal Workflow Items\n\nFor every speckit command session:\n\n```\n- [ ] Verify repository context and .specify/ structure\n- [ ] Validate prerequisites (scripts, dependencies, templates)\n- [ ] Load command-specific skills\n- [ ] Execute command workflow\n- [ ] Verify artifacts created/updated\n- [ ] Complete progress tracking\n```\n\n### Specification Phase Items\n\n**`/speckit-specify`**\n```\n- [ ] Load spec-writing and brainstorming skills\n- [ ] Analyze feature description and requirements\n- [ ] Generate/update spec.md with template\n- [ ] Verify spec.md contains all required sections\n- [ ] Validate frontmatter metadata\n```\n\n**`/speckit-clarify`**\n```\n- [ ] Read existing spec.md\n- [ ] Identify underspecified areas\n- [ ] Ask targeted clarification questions (max 5)\n- [ ] Encode answers back into spec.md\n- [ ] Verify improved specification completeness\n```\n\n**`/speckit-constitution`**\n```\n- [ ] Gather project principles (interactive or provided)\n- [ ] Create/update constitution.md\n- [ ] Sync dependent templates with constitution\n- [ ] Verify template consistency\n```\n\n### Planning Phase Items\n\n**`/speckit-plan`**\n```\n- [ ] Load task-planning and writing-plans skills\n- [ ] Read spec.md and constitution.md\n- [ ] Execute planning template workflow\n- [ ] Generate plan.md with design artifacts\n- [ ] Verify plan completeness and consistency\n```\n\n**`/speckit-tasks`**\n```\n- [ ] Read all available design artifacts (spec, plan, constitution)\n- [ ] Analyze dependencies and ordering constraints\n- [ ] Generate tasks.md with concrete tasks\n- [ ] Verify task ordering and completeness\n- [ ] Mark tasks ready for implementation\n```\n\n### Implementation Phase Items\n\n**`/speckit-implement`**\n```\n- [ ] Load executing-plans skill\n- [ ] Read and parse tasks.md\n- [ ] Execute tasks in dependency order\n- [ ] Track completion status per task\n- [ ] Handle errors with systematic-debugging\n- [ ] Verify all tasks completed successfully\n```\n\n### Verification Phase Items\n\n**`/speckit-analyze`**\n```\n- [ ] Read spec.md, plan.md, tasks.md\n- [ ] Check cross-artifact consistency\n- [ ] Identify quality issues\n- [ ] Generate analysis report\n- [ ] Provide concrete recommendations with evidence\n```\n\n**`/speckit-checklist`**\n```\n- [ ] Read feature requirements from spec.md\n- [ ] Generate custom verification checklist\n- [ ] Output checklist in markdown format\n- [ ] Verify checklist completeness\n```\n\n## Workflow Phase Tracking\n\n### Phase States\n\n1. **Not Started**: Prerequisites not yet validated\n2. **In Progress**: Command executing, artifacts being created\n3. **Blocked**: Waiting for user input or error resolution\n4. **Completed**: Artifacts created, verification passed\n5. **Failed**: Unrecoverable error, manual intervention needed\n\n### Phase Transitions\n\n```\nNot Started → In Progress: When prerequisites validated\nIn Progress → Blocked: When user input or clarification needed\nIn Progress → Failed: When unrecoverable error occurs\nIn Progress → Completed: When all exit criteria met\nBlocked → In Progress: When blocker resolved\n```\n\n### Status Reporting\n\nAfter each phase transition, report:\n- Current phase and status\n- Artifacts created/modified\n- Outstanding blockers (if any)\n- Next steps\n\n## Completion Verification Patterns\n\n### Specification Phase Verification\n\n- [ ] spec.md exists and is valid markdown\n- [ ] All required frontmatter fields present\n- [ ] All template sections completed\n- [ ] No placeholder text remains\n- [ ] Acceptance criteria are testable\n\n### Planning Phase Verification\n\n- [ ] plan.md exists and follows template\n- [ ] Design decisions documented with rationale\n- [ ] Architecture diagrams/descriptions present\n- [ ] Technical approach is clear\n- [ ] Risks and mitigations identified\n\n### Task Generation Verification\n\n- [ ] tasks.md exists with concrete tasks\n- [ ] Tasks are dependency-ordered\n- [ ] Each task has clear completion criteria\n- [ ] File paths and locations specified\n- [ ] Verification steps included\n\n### Implementation Phase Verification\n\n- [ ] All tasks in tasks.md completed\n- [ ] Code compiles/runs successfully\n- [ ] Tests pass (if applicable)\n- [ ] No unresolved TODOs or FIXMEs\n- [ ] Documentation updated\n\n### Cross-Artifact Verification\n\n- [ ] spec.md requirements match plan.md design\n- [ ] plan.md design matches tasks.md implementation\n- [ ] tasks.md tasks align with spec.md acceptance criteria\n- [ ] No conflicting information across artifacts\n- [ ] Version/date metadata is consistent\n\n## Progress Persistence\n\n### Session Continuity\n\n- Track progress in TodoWrite for current session\n- Save state to artifacts (spec.md, plan.md, tasks.md)\n- Use frontmatter metadata for phase tracking\n- Enable `/catchup` recovery across sessions\n\n### Recovery Patterns\n\n**After Session Interruption**:\n1. Read artifact frontmatter to determine last phase\n2. Check artifact completeness vs. expected state\n3. Resume from last verified checkpoint\n4. Re-validate prerequisites if needed\n\n**After Error**:\n1. Mark current phase as blocked\n2. Document error and attempted solutions\n3. Load systematic-debugging if needed\n4. Clear blocker, then resume progress\n\n## Metrics and Reporting\n\n### Track Per Session\n\n- Total workflow duration\n- Time per phase\n- Number of iterations (clarify, refactor)\n- Artifact sizes (lines, tokens)\n- User interactions required\n\n### Quality Metrics\n\n- Specification completeness score\n- Plan-spec alignment score\n- Task-plan alignment score\n- Cross-artifact consistency score\n\nFile v1.9.16:modules/writing-plans-extensions.md\n\n# Writing-Plans Extensions for Spec-kit\n\n## Overview\n\nThis document defines the extensions that spec-kit provides to enhance the `superpowers:writing-plans` skill with specification-driven artifact management, quality validation, and workflow integration.\n\n## Extension Categories\n\n### 1. Artifact Management Extensions\n\n#### Artifact Lifecycle Management\n```python\nclass ArtifactManager:\n def track_artifact_lifecycle(self, artifact_path: str) -> ArtifactStatus\n def validate_artifact_consistency(self, artifacts: List[str]) -> ConsistencyReport\n def generate_artifact_summary(self, phase: str) -> ArtifactSummary\n def detect_artifact_changes(self, since_timestamp: datetime) -> ChangeReport\n```\n\n#### Specification-Driven Artifact Generation\n- **Templates**: Use spec-kit templates for consistent artifact structure\n- **Cross-References**: Maintain bidirectional links between artifacts\n- **Version Control**: Track artifact versions and changes\n- **Quality Gates**: Apply spec-kit quality validation to all artifacts\n\n#### Artifact Types Managed\n1. **spec.md** - Feature specifications with user stories\n2. **plan.md** - Implementation plans with tech decisions\n3. **data-model.md** - Entity relationships and validation\n4. **contracts/** - API specifications and schemas\n5. **research.md** - Technical decisions and rationale\n6. **tasks.md** - Dependency-ordered implementation tasks\n7. **checklists/** - Quality validation checklists\n\n### 2. Quality Validation Extensions\n\n#### Specification-Driven Quality Gates\n```python\nclass QualityGateValidator:\n def validate_specification_completeness(self, spec_path: str) -> SpecQualityReport\n def validate_plan_consistency(self, plan_path: str, spec_path: str) -> ConsistencyReport\n def validate_task_completeness(self, tasks_path: str, plan_path: str) -> TaskQualityReport\n def validate_cross_artifact_alignment(self, artifacts: Dict[str, str]) -> AlignmentReport\n```\n\n#### Quality Criteria\n- **Specification Quality**: No implementation details, measurable success criteria\n- **Plan Consistency**: Tech decisions align with specifications\n- **Task Completeness**: All requirements have corresponding tasks\n- **Cross-Artifact Alignment**: No contradictions between artifacts\n\n#### Validation Reports\n```json\n{\n \"validation_timestamp\": \"2025-12-08T13:45:00Z\",\n \"overall_status\": \"pass\",\n \"artifact_validations\": {\n \"spec.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"completeness_score\": 0.95\n },\n \"plan.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"consistency_score\": 0.98\n }\n },\n \"cross_artifact_issues\": [],\n \"recommendations\": []\n}\n```\n\n### 3. Workflow Integration Extensions\n\n#### Phase Transition Management\n```python\nclass WorkflowOrchestrator:\n def transition_to_planning(self, spec_path: str) -> PlanningContext\n def transition_to_implementation(self, tasks_path: str) -> ImplementationContext\n def validate_phase_completion(self, phase: str, artifacts: List[str]) -> CompletionReport\n def generate_phase_summary(self, phase: str) -> PhaseSummary\n```\n\n#### Session Persistence\n- **State Management**: Maintain workflow state across sessions\n- **Progress Tracking**: Track completion of workflow phases\n- **Context Restoration**: Restore session state on restart\n- **Checkpoint System**: Create and restore checkpoints\n\n#### Skill Coordination\n- **Loading Order**: Optimize skill loading for maximum efficiency\n- **State Sharing**: Coordinate state between skills\n- **Conflict Resolution**: Handle conflicts between skill outputs\n- **Resource Management**: Optimize resource usage across skills\n\n### 4. Enhanced Planning Extensions\n\n#### Specification-Driven Task Generation\n```python\nclass SpecificationDrivenPlanner:\n def extract_user_stories(self, spec_path: str) -> List[UserStory]\n def map_entities_to_stories(self, data_model_path: str, stories: List[UserStory]) -> Mapping\n def generate_story_based_tasks(self, stories: List[UserStory], plan_path: str) -> List[Task]\n def create_dependency_graph(self, tasks: List[Task]) -> DependencyGraph\n```\n\n#### User Story Organization\n- **Story-Based Phases**: Organize tasks by user story\n- **Independent Testing**: Create testable story increments\n- **MVP Identification**: Identify minimum viable product scope\n- **Parallel Execution**: Identify parallelizable tasks within stories\n\n#### Enhanced Task Features\n- **Strict Formatting**: Enforce spec-kit task formatting standards\n- **File Path Precision**: Include exact file paths for all tasks\n- **Dependency Clarity**: Explicit dependency specification\n- **Parallel Markers**: Clear identification of parallelizable tasks\n\n### 5. Traceability Extensions\n\n#### Requirement Traceability Matrix\n```python\nclass TraceabilityManager:\n def create_requirement_traceability(self, spec_path: str, tasks_path: str) -> TraceabilityMatrix\n def validate_implementation_coverage(self, spec_path: str, implementation_path: str) -> CoverageReport\n def generate_impact_analysis(self, requirement_change: str) -> ImpactReport\n```\n\n#### Traceability Features\n- **Bidirectional Links**: Links from requirements to tasks and vice versa\n- **Change Impact**: Analyze impact of requirement changes\n- **Coverage Analysis**: Verify all requirements are implemented\n- **Validation Mapping**: Map tests back to requirements\n\n#### Traceability Reports\n```markdown\n# Requirement Traceability Matrix\n\n| Requirement ID | User Story | Tasks | Test Cases | Status |\n|---------------|------------|-------|------------|--------|\n| REQ-001 | US1 | T001, T002, T003 | TC-001, TC-002 | Implemented |\n| REQ-002 | US2 | T004, T005 | TC-003 | In Progress |\n```\n\n### 6. Template Integration Extensions\n\n#### Template Enhancement\n- **Writing-Plans Integration**: Enhance spec-kit templates with writing-plans methodology\n- **Dynamic Content**: Generate template content based on context\n- **Validation Rules**: Embed validation rules in templates\n- **Best Practices**: Include writing-plans best practices in templates\n\n#### Custom Template Features\n```python\nclass TemplateEnhancer:\n def enhance_plan_template(self, base_template: str, writing_plans_context: dict) -> str\n def generate_contextual_content(self, template_section: str, context: dict) -> str\n def apply_best_practices(self, content: str, domain: str) -> str\n def validate_template_output(self, generated_content: str) -> ValidationReport\n```\n\n## Integration Benefits\n\n### For Writing-Plans Skill\n1. **Specification Context**: Access to detailed specifications for better planning\n2. **Quality Assurance**: Built-in validation and quality gates\n3. **Artifact Management**: Automatic artifact generation and tracking\n4. **Workflow Integration**: smooth integration into spec-kit workflow\n\n### For Spec-kit Plugin\n1. **Enhanced Planning**: Access to writing-plans' detailed methodology\n2. **Better Task Generation**: More detailed and accurate task breakdown\n3. **Improved Quality**: Better validation and consistency checking\n4. **Session Management**: Enhanced session persistence and coordination\n\n## Usage Examples\n\n### Enhanced Planning Session\n```bash\n# Start enhanced session\n/speckit-startup.wrapped\n\n# Generate specification with writing-plans refinement\n/speckit-specify \"Add user authentication system\"\n\n# Create enhanced plan with writing-plans methodology\n/speckit-plan.wrapped\n\n# Generate detailed tasks with specification-driven organization\n/speckit-tasks.wrapped\n```\n\n### Quality Validation\n```python\n# Run detailed quality validation\nquality_report = validator.validate_cross_artifact_alignment({\n 'spec.md': '/specs/1-user-auth/spec.md',\n 'plan.md': '/specs/1-user-auth/plan.md',\n 'tasks.md': '/specs/1-user-auth/tasks.md'\n})\n\nprint(f\"Overall quality: {quality_report.overall_status}\")\nprint(f\"Issues found: {len(quality_report.cross_artifact_issues)}\")\n```\n\n## Configuration\n\n### Extension Activation\n```yaml\n# .specify/config/extensions.yml\nwriting_plans_extensions:\n enabled: true\n artifact_management: true\n quality_validation: true\n workflow_integration: true\n traceability: true\n template_enhancement: true\n```\n\n### Quality Gate Configuration\n```yaml\nquality_gates:\n specification:\n completeness_threshold: 0.9\n max_clarifications: 3\n success_criteria_required: true\n\n planning:\n consistency_threshold: 0.85\n dependency_validation: true\n task_formatting: strict\n\n implementation:\n coverage_threshold: 0.95\n test_coverage: true\n quality_checks: automated\n```\n\nThis specification provides the foundation for integrating spec-kit's artifact management and quality validation capabilities with the superpowers:writing-plans skill, creating a detailed planning and execution system.\n\nFile v1.9.16:skill-card.md\n\n## Description:
\nOrchestrates Spec Driven Development by coordinating spec, plan, and task skills.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to coordinate spec-driven workflows across specification, planning, task generation, implementation, and verification phases.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may be invoked by generic planning or workflow language outside an intended spec-kit project.
\nMitigation: Confirm the active project uses spec-kit before applying the skill to read or update specification, planning, task, and checklist files.
\nRisk: Generated workflow guidance can produce incorrect or misleading changes to project artifacts if used without review.
\nMitigation: Review proposed artifact changes and run project-specific validation before deployment or release.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-spec-kit-speckit-orchestrator)
\n- [Project Homepage](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, markdown, configuration]
\n**Output Format:** [Markdown guidance with checklists, workflow steps, and configuration examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Coordinates existing spec-kit artifacts and related skills; no executable payloads are included in the release artifact.]
\n\n## Skill Version(s):
\n1.9.16 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.14: 7 files, 13578 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5698b), modules/writing-plans-extensions.md (8735b), skill-card.md (2478b), SKILL.md (4533b), _meta.json (152b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: speckit-orchestrator\ndescription: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\nversion: 1.9.8\ntriggers:\n - speckit\n - workflow\n - orchestration\n - planning\n - specification\n - running the full speckit workflow from spec to implementation\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.superpowers:brainstorming\", \"night-market.superpowers:writing-plans\", \"night-market.superpowers:executing-plans\"]}}}\nsource: claude-night-market\nsource_plugin: spec-kit\n---\n\n> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Persistent Presence Lens](#persistent-presence-lens)\n- [When to Use](#when-to-use)\n- [Core Workflow](#core-workflow)\n- [Session Initialization](#session-initialization)\n- [Command-Skill Matrix](#command-skill-matrix)\n- [Progress Tracking Items](#progress-tracking-items)\n- [Exit Criteria](#exit-criteria)\n- [Related Skills](#related-skills)\n\n\n# Speckit Orchestrator\n\n## Overview\n\nCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.\n\n## Persistent Presence Lens\n\nTreat SDD as a minimal, testable \"self-modeling\" loop:\n\n- **World model**: repo + speckit artifacts (`spec.md`, `plan.md`, `tasks.md`)\n- **Agent model**: loaded skills/plugins + constraints (especially `.specify/memory/constitution.md`) + progress state\n\nThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (`tasks.md`) and a skill library (reusable plugin skills and superpowers methodology skills).\n\n## When To Use\n\n- Starting any `/speckit-*` command.\n- Coordinating multi-phase development workflows.\n- Tracking progress across specification, planning, and implementation.\n- Ensuring skill dependencies are loaded.\n\n## When NOT To Use\n\n- Single-phase work (just specify, or just plan)\n- Non-spec-driven projects\n\n## Core Workflow\n\n### Session Initialization\n\n1. **Verify Repository Context**\n - Confirm working directory is a speckit-enabled project.\n - Check for `.specify/` directory structure.\n - Validate required scripts exist.\n\n2. **Load Persistent State (\"presence\")**\n - Read `.specify/memory/constitution.md` for constraints/principles.\n - Load current `spec.md` / `plan.md` / `tasks.md` context if present.\n\n3. **Load Command Dependencies**\n - Match current command to required skills.\n - Load complementary superpowers skills.\n\n4. **Initialize Progress Tracking**\n - Create TodoWrite items for workflow phases.\n - Track completion status.\n\n### Command-Skill Matrix\n\nQuick reference for command-to-skill mappings:\n\n| Command | Primary Skill | Complementary Skills |\n|---------|--------------|---------------------|\n| `/speckit-specify` | spec-writing | brainstorming |\n| `/speckit-clarify` | spec-writing | brainstorming |\n| `/speckit-plan` | task-planning | writing-plans |\n| `/speckit-tasks` | task-planning | executing-plans |\n| `/speckit-implement` | - | executing-plans, systematic-debugging |\n| `/speckit-analyze` | - | systematic-debugging, verification |\n| `/speckit-checklist` | - | verification-before-completion |\n\n**For detailed patterns**: See `modules/command-skill-matrix.md` for complete mappings and loading rules.\n\nSee `modules/writing-plans-extensions.md` for plan authoring patterns.\n\n### Progress Tracking Items\n\nFor each workflow session, track:\n- [ ] Repository context verified.\n- [ ] Prerequisites validated.\n- [ ] Command-specific skills loaded.\n- [ ] Artifacts created/updated.\n- [ ] Verification completed.\n\n**For detailed patterns**: See `modules/progress-tracking.md` for TodoWrite patterns and metrics.\n\n## Exit Criteria\n\n- Active command completed successfully.\n- All required artifacts exist and are valid.\n- Progress tracking reflects current state.\n- No unresolved blockers.\n\n## Related Skills\n\n- `spec-writing`: Specification creation and refinement.\n- `task-planning`: Task generation and planning.\n- `superpowers:brainstorming`: Idea refinement.\n- `superpowers:writing-plans`: Implementation planning.\n- `superpowers:executing-plans`: Task execution.\n\nFile v1.9.14:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-spec-kit-speckit-orchestrator\",\n \"version\": \"1.9.14\",\n \"publishedAt\": 1782842834088\n}\n\nFile v1.9.14:modules/artifact-structure.md\n\n---\nname: artifact-structure\ndescription: Documentation of spec-kit artifact structure, purposes, and organization\ncategory: reference\ntags: [artifacts, structure, organization, documentation]\ndependencies: [speckit-orchestrator]\ncomplexity: beginner\nestimated_tokens: 800\n---\n\n# Spec-Kit Artifact Structure\n\n## Overview\n\nSpec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.\n\n## Directory Structure\n\n```\nproject-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/\n```\n\n> **Note: Claude Code Plan Mode Namespace**\n>\n> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the\n> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.\n> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid\n> collision. When searching for scope artifacts:\n> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)\n> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)\n>\n> The two systems are complementary: Claude Plan Mode is for exploratory planning,\n> while spec-kit plans are structured implementation blueprints.\n\n## Core Artifacts\n\n### spec.md - Feature Specification\n\n**Purpose**: Define WHAT users need and WHY, without implementation details.\n\n**Audience**: Business stakeholders, product managers, non-technical reviewers.\n\n**Structure**:\n```markdown\n# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Technology-agnostic metrics\n- User-facing goals\n\n## Success Criteria (Optional)\n- Performance expectations\n- Security considerations\n- Accessibility needs\n\n## Edge Cases (Optional)\n- Boundary conditions\n- Error scenarios\n- Fallback behaviors\n\n## Dependencies & Assumptions (Optional)\n- External dependencies\n- Documented assumptions\n```\n\n**Key Principles**:\n- No technology choices (no \"React\", \"PostgreSQL\", \"REST API\")\n- Focus on user value, not system internals\n- Measurable, testable requirements\n- Maximum 3 [NEEDS CLARIFICATION] markers\n\n### plan.md - Implementation Plan\n\n**Purpose**: Define HOW to build the feature technically.\n\n**Audience**: Developers, technical leads, architects.\n\n**Structure**:\n```markdown\n# Implementation Plan: Feature Name\n\n## Technical Context\n- Tech stack decisions\n- Architecture choices\n- Libraries and frameworks\n\n## Constitution Check\n- Alignment with project principles\n- Gate evaluation\n\n## Phase 0: Research\n- Technical unknowns\n- Best practices research\n- Decision rationale\n\n## Phase 1: Design\n- Data model\n- API contracts\n- Integration points\n\n## Phase 2: Implementation\n- Component structure\n- Service layer\n- Infrastructure needs\n```\n\n**Key Principles**:\n- Technology-specific\n- Includes research and decisions\n- Maps to project constitution\n- Generates tasks.md\n\n### tasks.md - Implementation Tasks\n\n**Purpose**: Actionable, dependency-ordered tasks for implementation.\n\n**Audience**: Developers executing the feature.\n\n**Structure**:\n```markdown\n# Implementation Tasks: Feature Name\n\n## Overview\n- Total tasks\n- Parallelization opportunities\n- MVP scope\n\n## Dependencies\n- User story completion order\n- Blocking prerequisites\n\n## Phase 1: Setup\n- [ ] T001 Project initialization\n- [ ] T002 [P] Configure tooling\n\n## Phase 2: Foundational\n- [ ] T010 Shared infrastructure\n\n## Phase 3: User Story 1 (P1)\n- [ ] T020 [US1] Model creation\n- [ ] T021 [P] [US1] Service implementation\n- [ ] T022 [US1] Endpoint implementation\n\n## Phase 4: User Story 2 (P2)\n- [ ] T030 [US2] Feature implementation\n\n## Final Phase: Polish\n- [ ] T090 Cross-cutting concerns\n- [ ] T091 Documentation\n```\n\n**Task Format**:\n```\n- [ ] [TaskID] [P?] [Story?] Description with file path\n```\n\n**Key Principles**:\n- Organized by user story\n- Sequential task IDs\n- Clear parallelization markers [P]\n- Story labels [US1], [US2], etc.\n- Explicit file paths\n\n### checklists/ - Quality Validation\n\n**Purpose**: \"Unit tests for requirements\" - validate requirement quality.\n\n**Audience**: Spec authors, reviewers, QA.\n\n**Structure**: Multiple domain-specific checklists:\n- `requirements.md` - Overall spec quality\n- `ux.md` - UX requirements validation\n- `api.md` - API requirements validation\n- `security.md` - Security requirements validation\n- `performance.md` - Performance requirements validation\n\n**Checklist Item Format**:\n```markdown\n- [ ] CHK001 Are [requirements] defined for [scenario]? [Dimension, Reference]\n```\n\n**Key Principles**:\n- Test requirements quality, NOT implementation\n- Focus on completeness, clarity, consistency\n- ≥80% traceability to spec sections\n- Question format, not verification statements\n\n## Supporting Artifacts\n\n### research.md\nDocuments technical research, decisions, and alternatives considered during Phase 0.\n\n### data-model.md\nDefines entities, fields, relationships, validation rules, and state transitions.\n\n### quickstart.md\nTest scenarios and acceptance testing guides for the feature.\n\n### contracts/\nAPI contracts (OpenAPI, GraphQL schemas) generated from functional requirements.\n\n## Workflow Progression\n\n1. **Specify**: Create spec.md (user-focused, no tech)\n2. **Clarify**: Resolve [NEEDS CLARIFICATION] markers\n3. **Checklist**: Validate spec quality with requirements.md checklist\n4. **Plan**: Create plan.md (technical design)\n5. **Tasks**: Generate tasks.md (actionable implementation)\n6. **Implement**: Execute tasks, mark complete\n7. **Validate**: Domain-specific checklists (ux.md, api.md, etc.)\n\n## Artifact Relationships\n\n```\nspec.md (WHAT/WHY)\n ↓\nchecklists/requirements.md (validate spec)\n ↓\nplan.md (HOW)\n ↓\ntasks.md (DO)\n ↓\nchecklists/[domain].md (validate implementation requirements)\n```\n\n## Usage in Commands\n\n- `/speckit-specify` → Creates spec.md, checklists/requirements.md\n- `/speckit-clarify` → Resolves [NEEDS CLARIFICATION] in spec.md\n- `/speckit-plan` → Creates plan.md, research.md, data-model.md, contracts/\n- `/speckit-tasks` → Generates tasks.md from plan.md + spec.md\n- `/speckit-checklist` → Creates domain-specific checklists (ux.md, api.md, etc.)\n- `/speckit-implement` → Executes tasks.md\n- `/speckit-analyze` → Cross-artifact consistency validation\n\nFile v1.9.14:modules/command-skill-matrix.md\n\n# Command-Skill Matrix\n\n## Overview\n\nThe Command-Skill Matrix defines which skills are required for each speckit command, ensuring proper dependencies are loaded and coordinated throughout the workflow.\n\n## Complete Mapping\n\n### Specification Phase\n\n**`/speckit-specify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: At command start, before any specification work\n- **Purpose**: Create or refine feature specifications with collaborative ideation\n\n**`/speckit-clarify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: When specification needs refinement or has gaps\n- **Purpose**: Identify underspecified areas and encode clarifications\n\n**`/speckit-constitution`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: None required\n- **Loading Order**: spec-writing only\n- **When to Load**: Creating or updating project principles\n- **Purpose**: Establish project governance and design principles\n\n### Planning Phase\n\n**`/speckit-plan`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:writing-plans`\n- **Loading Order**: task-planning → writing-plans\n- **When to Load**: After specification is complete\n- **Purpose**: Generate detailed implementation design artifacts\n\n**`/speckit-tasks`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:executing-plans`\n- **Loading Order**: task-planning → executing-plans\n- **When to Load**: After planning artifacts exist\n- **Purpose**: Generate dependency-ordered implementation tasks\n\n### Implementation Phase\n\n**`/speckit-implement`**\n- **Primary Skill**: None (uses loaded plan)\n- **Complementary Skills**: `superpowers:executing-plans`, `superpowers:systematic-debugging`\n- **Loading Order**: executing-plans → systematic-debugging (on-demand)\n- **When to Load**: When executing tasks from tasks.md\n- **Purpose**: Execute implementation tasks with error handling\n\n### Verification Phase\n\n**`/speckit-analyze`**\n- **Primary Skill**: None (analysis only)\n- **Complementary Skills**: `superpowers:systematic-debugging`, `superpowers:verification-before-completion`\n- **Loading Order**: Load both at analysis start\n- **When to Load**: After task generation or implementation\n- **Purpose**: Cross-artifact consistency and quality analysis\n\n**`/speckit-checklist`**\n- **Primary Skill**: None (generation only)\n- **Complementary Skills**: `superpowers:verification-before-completion`\n- **Loading Order**: verification-before-completion only\n- **When to Load**: When generating feature-specific checklists\n- **Purpose**: Create custom verification checklists\n\n**`/speckit-startup`**\n- **Primary Skill**: None (bootstrap only)\n- **Complementary Skills**: None required\n- **Loading Order**: N/A\n- **When to Load**: Session initialization\n- **Purpose**: Bootstrap workflow and verify environment\n\n## Skill Loading Priorities\n\n### High Priority (Always Load First)\n1. `spec-writing` - For any specification work\n2. `task-planning` - For any planning work\n\n### Medium Priority (Load After Primary)\n3. `superpowers:brainstorming` - For ideation phases\n4. `superpowers:writing-plans` - For detailed planning\n5. `superpowers:executing-plans` - For implementation\n\n### Low Priority (Load On-Demand)\n6. `superpowers:systematic-debugging` - When errors occur\n7. `superpowers:verification-before-completion` - For final checks\n\n## Conditional Loading Rules\n\n- **Brainstorming**: Only load if specification is new or incomplete\n- **Systematic Debugging**: Only load if implementation encounters errors\n- **Verification**: Only load for analyze/checklist commands or before completion\n- **Writing Plans**: Only load if creating new implementation plans\n\n## Skill Interaction Patterns\n\n### Specification → Planning\n- Specification skills complete → task-planning loads\n- Hand off spec.md to planning phase\n\n### Planning → Implementation\n- Planning skills complete → executing-plans loads\n- Hand off tasks.md to implementation phase\n\n### Implementation → Verification\n- Implementation errors → systematic-debugging loads\n- Implementation complete → verification-before-completion loads\n\nFile v1.9.14:modules/progress-tracking.md\n\n# Progress Tracking\n\n## Overview\n\nDefines TodoWrite item patterns and progress tracking strategies for speckit workflows. validates consistent status reporting and verification throughout all workflow phases.\n\n## TodoWrite Item Patterns\n\n### Universal Workflow Items\n\nFor every speckit command session:\n\n```\n- [ ] Verify repository context and .specify/ structure\n- [ ] Validate prerequisites (scripts, dependencies, templates)\n- [ ] Load command-specific skills\n- [ ] Execute command workflow\n- [ ] Verify artifacts created/updated\n- [ ] Complete progress tracking\n```\n\n### Specification Phase Items\n\n**`/speckit-specify`**\n```\n- [ ] Load spec-writing and brainstorming skills\n- [ ] Analyze feature description and requirements\n- [ ] Generate/update spec.md with template\n- [ ] Verify spec.md contains all required sections\n- [ ] Validate frontmatter metadata\n```\n\n**`/speckit-clarify`**\n```\n- [ ] Read existing spec.md\n- [ ] Identify underspecified areas\n- [ ] Ask targeted clarification questions (max 5)\n- [ ] Encode answers back into spec.md\n- [ ] Verify improved specification completeness\n```\n\n**`/speckit-constitution`**\n```\n- [ ] Gather project principles (interactive or provided)\n- [ ] Create/update constitution.md\n- [ ] Sync dependent templates with constitution\n- [ ] Verify template consistency\n```\n\n### Planning Phase Items\n\n**`/speckit-plan`**\n```\n- [ ] Load task-planning and writing-plans skills\n- [ ] Read spec.md and constitution.md\n- [ ] Execute planning template workflow\n- [ ] Generate plan.md with design artifacts\n- [ ] Verify plan completeness and consistency\n```\n\n**`/speckit-tasks`**\n```\n- [ ] Read all available design artifacts (spec, plan, constitution)\n- [ ] Analyze dependencies and ordering constraints\n- [ ] Generate tasks.md with concrete tasks\n- [ ] Verify task ordering and completeness\n- [ ] Mark tasks ready for implementation\n```\n\n### Implementation Phase Items\n\n**`/speckit-implement`**\n```\n- [ ] Load executing-plans skill\n- [ ] Read and parse tasks.md\n- [ ] Execute tasks in dependency order\n- [ ] Track completion status per task\n- [ ] Handle errors with systematic-debugging\n- [ ] Verify all tasks completed successfully\n```\n\n### Verification Phase Items\n\n**`/speckit-analyze`**\n```\n- [ ] Read spec.md, plan.md, tasks.md\n- [ ] Check cross-artifact consistency\n- [ ] Identify quality issues\n- [ ] Generate analysis report\n- [ ] Provide concrete recommendations with evidence\n```\n\n**`/speckit-checklist`**\n```\n- [ ] Read feature requirements from spec.md\n- [ ] Generate custom verification checklist\n- [ ] Output checklist in markdown format\n- [ ] Verify checklist completeness\n```\n\n## Workflow Phase Tracking\n\n### Phase States\n\n1. **Not Started**: Prerequisites not yet validated\n2. **In Progress**: Command executing, artifacts being created\n3. **Blocked**: Waiting for user input or error resolution\n4. **Completed**: Artifacts created, verification passed\n5. **Failed**: Unrecoverable error, manual intervention needed\n\n### Phase Transitions\n\n```\nNot Started → In Progress: When prerequisites validated\nIn Progress → Blocked: When user input or clarification needed\nIn Progress → Failed: When unrecoverable error occurs\nIn Progress → Completed: When all exit criteria met\nBlocked → In Progress: When blocker resolved\n```\n\n### Status Reporting\n\nAfter each phase transition, report:\n- Current phase and status\n- Artifacts created/modified\n- Outstanding blockers (if any)\n- Next steps\n\n## Completion Verification Patterns\n\n### Specification Phase Verification\n\n- [ ] spec.md exists and is valid markdown\n- [ ] All required frontmatter fields present\n- [ ] All template sections completed\n- [ ] No placeholder text remains\n- [ ] Acceptance criteria are testable\n\n### Planning Phase Verification\n\n- [ ] plan.md exists and follows template\n- [ ] Design decisions documented with rationale\n- [ ] Architecture diagrams/descriptions present\n- [ ] Technical approach is clear\n- [ ] Risks and mitigations identified\n\n### Task Generation Verification\n\n- [ ] tasks.md exists with concrete tasks\n- [ ] Tasks are dependency-ordered\n- [ ] Each task has clear completion criteria\n- [ ] File paths and locations specified\n- [ ] Verification steps included\n\n### Implementation Phase Verification\n\n- [ ] All tasks in tasks.md completed\n- [ ] Code compiles/runs successfully\n- [ ] Tests pass (if applicable)\n- [ ] No unresolved TODOs or FIXMEs\n- [ ] Documentation updated\n\n### Cross-Artifact Verification\n\n- [ ] spec.md requirements match plan.md design\n- [ ] plan.md design matches tasks.md implementation\n- [ ] tasks.md tasks align with spec.md acceptance criteria\n- [ ] No conflicting information across artifacts\n- [ ] Version/date metadata is consistent\n\n## Progress Persistence\n\n### Session Continuity\n\n- Track progress in TodoWrite for current session\n- Save state to artifacts (spec.md, plan.md, tasks.md)\n- Use frontmatter metadata for phase tracking\n- Enable `/catchup` recovery across sessions\n\n### Recovery Patterns\n\n**After Session Interruption**:\n1. Read artifact frontmatter to determine last phase\n2. Check artifact completeness vs. expected state\n3. Resume from last verified checkpoint\n4. Re-validate prerequisites if needed\n\n**After Error**:\n1. Mark current phase as blocked\n2. Document error and attempted solutions\n3. Load systematic-debugging if needed\n4. Clear blocker, then resume progress\n\n## Metrics and Reporting\n\n### Track Per Session\n\n- Total workflow duration\n- Time per phase\n- Number of iterations (clarify, refactor)\n- Artifact sizes (lines, tokens)\n- User interactions required\n\n### Quality Metrics\n\n- Specification completeness score\n- Plan-spec alignment score\n- Task-plan alignment score\n- Cross-artifact consistency score\n\nFile v1.9.14:modules/writing-plans-extensions.md\n\n# Writing-Plans Extensions for Spec-kit\n\n## Overview\n\nThis document defines the extensions that spec-kit provides to enhance the `superpowers:writing-plans` skill with specification-driven artifact management, quality validation, and workflow integration.\n\n## Extension Categories\n\n### 1. Artifact Management Extensions\n\n#### Artifact Lifecycle Management\n```python\nclass ArtifactManager:\n def track_artifact_lifecycle(self, artifact_path: str) -> ArtifactStatus\n def validate_artifact_consistency(self, artifacts: List[str]) -> ConsistencyReport\n def generate_artifact_summary(self, phase: str) -> ArtifactSummary\n def detect_artifact_changes(self, since_timestamp: datetime) -> ChangeReport\n```\n\n#### Specification-Driven Artifact Generation\n- **Templates**: Use spec-kit templates for consistent artifact structure\n- **Cross-References**: Maintain bidirectional links between artifacts\n- **Version Control**: Track artifact versions and changes\n- **Quality Gates**: Apply spec-kit quality validation to all artifacts\n\n#### Artifact Types Managed\n1. **spec.md** - Feature specifications with user stories\n2. **plan.md** - Implementation plans with tech decisions\n3. **data-model.md** - Entity relationships and validation\n4. **contracts/** - API specifications and schemas\n5. **research.md** - Technical decisions and rationale\n6. **tasks.md** - Dependency-ordered implementation tasks\n7. **checklists/** - Quality validation checklists\n\n### 2. Quality Validation Extensions\n\n#### Specification-Driven Quality Gates\n```python\nclass QualityGateValidator:\n def validate_specification_completeness(self, spec_path: str) -> SpecQualityReport\n def validate_plan_consistency(self, plan_path: str, spec_path: str) -> ConsistencyReport\n def validate_task_completeness(self, tasks_path: str, plan_path: str) -> TaskQualityReport\n def validate_cross_artifact_alignment(self, artifacts: Dict[str, str]) -> AlignmentReport\n```\n\n#### Quality Criteria\n- **Specification Quality**: No implementation details, measurable success criteria\n- **Plan Consistency**: Tech decisions align with specifications\n- **Task Completeness**: All requirements have corresponding tasks\n- **Cross-Artifact Alignment**: No contradictions between artifacts\n\n#### Validation Reports\n```json\n{\n \"validation_timestamp\": \"2025-12-08T13:45:00Z\",\n \"overall_status\": \"pass\",\n \"artifact_validations\": {\n \"spec.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"completeness_score\": 0.95\n },\n \"plan.md\": {\n \"status\": \"pass\",\n \"issues\": [],\n \"consistency_score\": 0.98\n }\n },\n \"cross_artifact_issues\": [],\n \"recommendations\": []\n}\n```\n\n### 3. Workflow Integration Extensions\n\n#### Phase Transition Management\n```python\nclass WorkflowOrchestrator:\n def transition_to_planning(self, spec_path: str) -> PlanningContext\n def transition_to_implementation(self, tasks_path: str) -> ImplementationContext\n def validate_phase_completion(self, phase: str, artifacts: List[str]) -> CompletionReport\n def generate_phase_summary(self, phase: str) -> PhaseSummary\n```\n\n#### Session Persistence\n- **State Management**: Maintain workflow state across sessions\n- **Progress Tracking**: Track completion of workflow phases\n- **Context Restoration**: Restore session state on restart\n- **Checkpoint System**: Create and restore checkpoints\n\n#### Skill Coordination\n- **Loading Order**: Optimize skill loading for maximum efficiency\n- **State Sharing**: Coordinate state between skills\n- **Conflict Resolution**: Handle conflicts between skill outputs\n- **Resource Management**: Optimize resource usage across skills\n\n### 4. Enhanced Planning Extensions\n\n#### Specification-Driven Task Generation\n```python\nclass SpecificationDrivenPlanner:\n def extract_user_stories(self, spec_path: str) -> List[UserStory]\n def map_entities_to_stories(self, data_model_path: str, stories: List[UserStory]) -> Mapping\n def generate_story_based_tasks(self, stories: List[UserStory], plan_path: str) -> List[Task]\n def create_dependency_graph(self, tasks: List[Task]) -> DependencyGraph\n```\n\n#### User Story Organization\n- **Story-Based Phases**: Organize tasks by user story\n- **Independent Testing**: Create testable story increments\n- **MVP Identification**: Identify minimum viable product scope\n- **Parallel Execution**: Identify parallelizable tasks within stories\n\n#### Enhanced Task Features\n- **Strict Formatting**: Enforce spec-kit task formatting standards\n- **File Path Precision**: Include exact file paths for all tasks\n- **Dependency Clarity**: Explicit dependency specification\n- **Parallel Markers**: Clear identification of parallelizable tasks\n\n### 5. Traceability Extensions\n\n#### Requirement Traceability Matrix\n```python\nclass TraceabilityManager:\n def create_requirement_traceability(self, spec_path: str, tasks_path: str) -> TraceabilityMatrix\n def validate_implementation_coverage(self, spec_path: str, implementation_path: str) -> CoverageReport\n def generate_impact_analysis(self, requirement_change: str) -> ImpactReport\n```\n\n#### Traceability Features\n- **Bidirectional Links**: Links from requirements to tasks and vice versa\n- **Change Impact**: Analyze impact of requirement changes\n- **Coverage Analysis**: Verify all requirements are implemented\n- **Validation Mapping**: Map tests back to requirements\n\n#### Traceability Reports\n```markdown\n# Requirement Traceability Matrix\n\n| Requirement ID | User Story | Tasks | Test Cases | Status |\n|---------------|------------|-------|------------|--------|\n| REQ-001 | US1 | T001, T002, T003 | TC-001, TC-002 | Implemented |\n| REQ-002 | US2 | T004, T005 | TC-003 | In Progress |\n```\n\n### 6. Template Integration Extensions\n\n#### Template Enhancement\n- **Writing-Plans Integration**: Enhance spec-kit templates with writing-plans methodology\n- **Dynamic Content**: Generate template content based on context\n- **Validation Rules**: Embed validation rules in templates\n- **Best Practices**: Include writing-plans best practices in templates\n\n#### Custom Template Features\n```python\nclass TemplateEnhancer:\n def enhance_plan_template(self, base_template: str, writing_plans_context: dict) -> str\n def generate_contextual_content(self, template_section: str, context: dict) -> str\n def apply_best_practices(self, content: str, domain: str) -> str\n def validate_template_output(self, generated_content: str) -> ValidationReport\n```\n\n## Integration Benefits\n\n### For Writing-Plans Skill\n1. **Specification Context**: Access to detailed specifications for better planning\n2. **Quality Assurance**: Built-in validation and quality gates\n3. **Artifact Management**: Automatic artifact generation and tracking\n4. **Workflow Integration**: smooth integration into spec-kit workflow\n\n### For Spec-kit Plugin\n1. **Enhanced Planning**: Access to writing-plans' detailed methodology\n2. **Better Task Generation**: More detailed and accurate task breakdown\n3. **Improved Quality**: Better validation and consistency checking\n4. **Session Management**: Enhanced session persistence and coordination\n\n## Usage Examples\n\n### Enhanced Planning Session\n```bash\n# Start enhanced session\n/speckit-startup.wrapped\n\n# Generate specification with writing-plans refinement\n/speckit-specify \"Add user authentication system\"\n\n# Create enhanced plan with writing-plans methodology\n/speckit-plan.wrapped\n\n# Generate detailed tasks with specification-driven organization\n/speckit-tasks.wrapped\n```\n\n### Quality Validation\n```python\n# Run detailed quality validation\nquality_report = validator.validate_cross_artifact_alignment({\n 'spec.md': '/specs/1-user-auth/spec.md',\n 'plan.md': '/specs/1-user-auth/plan.md',\n 'tasks.md': '/specs/1-user-auth/tasks.md'\n})\n\nprint(f\"Overall quality: {quality_report.overall_status}\")\nprint(f\"Issues found: {len(quality_report.cross_artifact_issues)}\")\n```\n\n## Configuration\n\n### Extension Activation\n```yaml\n# .specify/config/extensions.yml\nwriting_plans_extensions:\n enabled: true\n artifact_management: true\n quality_validation: true\n workflow_integration: true\n traceability: true\n template_enhancement: true\n```\n\n### Quality Gate Configuration\n```yaml\nquality_gates:\n specification:\n completeness_threshold: 0.9\n max_clarifications: 3\n success_criteria_required: true\n\n planning:\n consistency_threshold: 0.85\n dependency_validation: true\n task_formatting: strict\n\n implementation:\n coverage_threshold: 0.95\n test_coverage: true\n quality_checks: automated\n```\n\nThis specification provides the foundation for integrating spec-kit's artifact management and quality validation capabilities with the superpowers:writing-plans skill, creating a detailed planning and execution system.\n\nFile v1.9.14:skill-card.md\n\n## Description:
\nOrchestrates Spec Driven Development by coordinating spec, plan, and task skills.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineers use this skill to coordinate Spec Driven Development workflows across specification, planning, task generation, implementation, and verification. It helps an agent load the right companion skills, track workflow progress, and keep Spec-Kit artifacts such as spec.md, plan.md, and tasks.md aligned.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad workflow and planning triggers may activate the skill outside an intended Spec-Kit session.
\nMitigation: Invoke it intentionally for Spec-Kit projects and confirm the current task is part of a spec, plan, task, implementation, or verification workflow.
\nRisk: Generated or modified Spec-Kit artifacts may encode incorrect requirements, plans, tasks, or verification guidance.
\nMitigation: Review generated or changed spec.md, plan.md, tasks.md, and checklist artifacts before proceeding to implementation.
\nRisk: The workflow expects related skills and configuration dependencies to be available.
\nMitigation: Confirm required companion skills and project Spec-Kit structure are present before relying on the orchestration guidance.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-spec-kit-speckit-orchestrator)
\n- [Configured metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline code, shell, and configuration snippets]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [No executable code is included in the release artifact; outputs are agent-facing workflow instructions and artifact guidance.]
\n\n## Skill Version(s):
\n1.9.14 (source: ClawHub release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.13: 7 files, 13588 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5698b), modules/writing-plans-extensions.md (8735b), skill-card.md (2396b), SKILL.md (4533b), _meta.json (152b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: speckit-orchestrator\ndescription: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\nversion: 1.9.8\ntriggers:\n - speckit\n - workflow\n - orchestration\n - planning\n - specification\n - running the full speckit workflow from spec to implementation\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.superpowers:brainstorming\", \"night-market.superpowers:writing-plans\", \"night-market.superpowers:executing-plans\"]}}}\nsource: claude-night-market\nsource_plugin: spec-kit\n---\n\n> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Persistent Presence Lens](#persistent-presence-lens)\n- [When to Use](#when-to-use)\n- [Core Workflow](#core-workflow)\n- [Session Initialization](#session-initialization)\n- [Command-Skill Matrix](#command-skill-matrix)\n- [Progress Tracking Items](#progress-tracking-items)\n- [Exit Criteria](#exit-criteria)\n- [Related Skills](#related-skills)\n\n\n# Speckit Orchestrator\n\n## Overview\n\nCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.\n\n## Persistent Presence Lens\n\nTreat SDD as a minimal, testable \"self-modeling\" loop:\n\n- **World model**: repo + speckit artifacts (`spec.md`, `plan.md`, `tasks.md`)\n- **Agent model**: loaded skills/plugins + constraints (especially `.specify/memory/constitution.md`) + progress state\n\nThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (`tasks.md`) and a skill library (reusable plugin skills and superpowers methodology skills).\n\n## When To Use\n\n- Starting any `/speckit-*` command.\n- Coordinating multi-phase development workflows.\n- Tracking progress across specification, planning, and implementation.\n- Ensuring skill dependencies are loaded.\n\n## When NOT To Use\n\n- Single-phase work (just specify, or just plan)\n- Non-spec-driven projects\n\n## Core Workflow\n\n### Session Initialization\n\n1. **Verify Repository Context**\n - Confirm working directory is a speckit-enabled project.\n - Check for `.specify/` directory structure.\n - Validate required scripts exist.\n\n2. **Load Persistent State (\"presence\")**\n - Read `.specify/memory/constitution.md` for constraints/principles.\n - Load current `spec.md` / `plan.md` / `tasks.md` context if present.\n\n3. **Load Command Dependencies**\n - Match current command to required skills.\n - Load complementary superpowers skills.\n\n4. **Initialize Progress Tracking**\n - Create TodoWrite items for workflow phases.\n - Track completion status.\n\n### Command-Skill Matrix\n\nQuick reference for command-to-skill mappings:\n\n| Command | Primary Skill | Complementary Skills |\n|---------|--------------|---------------------|\n| `/speckit-specify` | spec-writing | brainstorming |\n| `/speckit-clarify` | spec-writing | brainstorming |\n| `/speckit-plan` | task-planning | writing-plans |\n| `/speckit-tasks` | task-planning | executing-plans |\n| `/speckit-implement` | - | executing-plans, systematic-debugging |\n| `/speckit-analyze` | - | systematic-debugging, verification |\n| `/speckit-checklist` | - | verification-before-completion |\n\n**For detailed patterns**: See `modules/command-skill-matrix.md` for complete mappings and loading rules.\n\nSee `modules/writing-plans-extensions.md` for plan authoring patterns.\n\n### Progress Tracking Items\n\nFor each workflow session, track:\n- [ ] Repository context verified.\n- [ ] Prerequisites validated.\n- [ ] Command-specific skills loaded.\n- [ ] Artifacts created/updated.\n- [ ] Verification completed.\n\n**For detailed patterns**: See `modules/progress-tracking.md` for TodoWrite patterns and metrics.\n\n## Exit Criteria\n\n- Active command completed successfully.\n- All required artifacts exist and are valid.\n- Progress tracking reflects current state.\n- No unresolved blockers.\n\n## Related Skills\n\n- `spec-writing`: Specification creation and refinement.\n- `task-planning`: Task generation and planning.\n- `superpowers:brainstorming`: Idea refinement.\n- `superpowers:writing-plans`: Implementation planning.\n- `superpowers:executing-plans`: Task execution.\n\nFile v1.9.13:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-spec-kit-speckit-orchestrator\",\n \"version\": \"1.9.13\",\n \"publishedAt\": 1782577503553\n}\n\nFile v1.9.13:modules/artifact-structure.md\n\n---\nname: artifact-structure\ndescription: Documentation of spec-kit artifact structure, purposes, and organization\ncategory: reference\ntags: [artifacts, structure, organization, documentation]\ndependencies: [speckit-orchestrator]\ncomplexity: beginner\nestimated_tokens: 800\n---\n\n# Spec-Kit Artifact Structure\n\n## Overview\n\nSpec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.\n\n## Directory Structure\n\n```\nproject-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/\n```\n\n> **Note: Claude Code Plan Mode Namespace**\n>\n> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the\n> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.\n> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid\n> collision. When searching for scope artifacts:\n> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)\n> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)\n>\n> The two systems are complementary: Claude Plan Mode is for exploratory planning,\n> while spec-kit plans are structured implementation blueprints.\n\n## Core Artifacts\n\n### spec.md - Feature Specification\n\n**Purpose**: Define WHAT users need and WHY, without implementation details.\n\n**Audience**: Business stakeholders, product managers, non-technical reviewers.\n\n**Structure**:\n```markdown\n# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Te\n\nArchive v1.9.12: 7 files, 13442 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5698b), modules/writing-plans-extensions.md (8735b), skill-card.md (2064b), SKILL.md (4533b), _meta.json (152b)\n\nArchive v1.0.2: 7 files, 13709 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5690b), modules/writing-plans-extensions.md (8735b), skill-card.md (2429b), SKILL.md (4809b), _meta.json (151b)\n\nArchive v1.0.1: 6 files, 12468 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5690b), modules/writing-plans-extensions.md (8735b), SKILL.md (4809b), _meta.json (151b)\n\nArchive v1.0.0: 6 files, 12467 bytes\n\nFiles: modules/artifact-structure.md (7610b), modules/command-skill-matrix.md (4335b), modules/progress-tracking.md (5690b), modules/writing-plans-extensions.md (8735b), SKILL.md (4809b), _meta.json (151b)","readmeExcerpt":"Skill: speckit-orchestrator Owner: athola Summary: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:23:14.767Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:43:01.385Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:59:51.620Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:07:14.088Z | user Release v1.9.14 v1.9.13 | 2026-06-2","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"project-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/"},{"language":"markdown","snippet":"# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Technology-agnostic metrics\n- User-facing goals\n\n## Success Criteria (Optional)\n- Performance expectations\n- Security considerations\n- Accessibility needs\n\n## Edge Cases (Optional)\n- Boundary conditions\n- Error scenarios\n- Fallback behaviors\n\n## Dependencies & Assumptions (Optional)\n- External dependencies\n- Documented assumptions"},{"language":"markdown","snippet":"# Implementation Plan: Feature Name\n\n## Technical Context\n- Tech stack decisions\n- Architecture choices\n- Libraries and frameworks\n\n## Constitution Check\n- Alignment with project principles\n- Gate evaluation\n\n## Phase 0: Research\n- Technical unknowns\n- Best practices research\n- Decision rationale\n\n## Phase 1: Design\n- Data model\n- API contracts\n- Integration points\n\n## Phase 2: Implementation\n- Component structure\n- Service layer\n- Infrastructure needs"},{"language":"markdown","snippet":"# Implementation Tasks: Feature Name\n\n## Overview\n- Total tasks\n- Parallelization opportunities\n- MVP scope\n\n## Dependencies\n- User story completion order\n- Blocking prerequisites\n\n## Phase 1: Setup\n- [ ] T001 Project initialization\n- [ ] T002 [P] Configure tooling\n\n## Phase 2: Foundational\n- [ ] T010 Shared infrastructure\n\n## Phase 3: User Story 1 (P1)\n- [ ] T020 [US1] Model creation\n- [ ] T021 [P] [US1] Service implementation\n- [ ] T022 [US1] Endpoint implementation\n\n## Phase 4: User Story 2 (P2)\n- [ ] T030 [US2] Feature implementation\n\n## Final Phase: Polish\n- [ ] T090 Cross-cutting concerns\n- [ ] T091 Documentation"},{"language":"text","snippet":"- [ ] [TaskID] [P?] [Story?] Description with file path"},{"language":"markdown","snippet":"- [ ] CHK001 Are [requirements] defined for [scenario]? [Dimension, Reference]"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: speckit-orchestrator\ndescription: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills\nversion: 1.9.8\ntriggers:\n - speckit\n - workflow\n - orchestration\n - planning\n - specification\n - running the full speckit workflow from spec to implementation\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.superpowers:brainstorming\", \"night-market.superpowers:writing-plans\", \"night-market.superpowers:executing-plans\"]}}}\nsource: claude-night-market\nsource_plugin: spec-kit\n---\n\n> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Persistent Presence Lens](#persistent-presence-lens)\n- [When to Use](#when-to-use)\n- [Core Workflow](#core-workflow)\n- [Session Initialization](#session-initialization)\n- [Command-Skill Matrix](#command-skill-matrix)\n- [Progress Tracking Items](#progress-tracking-items)\n- [Exit Criteria](#exit-criteria)\n- [Related Skills](#related-skills)\n\n\n# Speckit Orchestrator\n\n## Overview\n\nCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.\n\n## Persistent Presence Lens\n\nTreat SDD as a minimal, testable \"self-modeling\" loop:\n\n- **World model**: repo + speckit artifacts (`spec.md`, `plan.md`, `tasks.md`)\n- **Agent model**: loaded skills/plugins + constraints (especially `.specify/memory/constitution.md`) + progress state\n\nThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (`tasks.md`) and a skill library (reusable plugin skills and superpowers methodology skills).\n\n## When To Use\n\n- Starting any `/speckit-*` command.\n- Coordinating multi-phase development workflows.\n- Tracking progress across specification, planning, and implementation.\n- Ensuring skill dependencies are loaded.\n\n## When NOT To Use\n\n- Single-phase work (just specify, or just plan)\n- Non-spec-driven projects\n\n## Core Workflow\n\n### Session Initialization\n\n1. **Verify Repository Context**\n - Confirm working directory is a speckit-enabled project.\n - Check for `.specify/` directory structure.\n - Validate required scripts exist.\n\n2. **Load Persistent State (\"presence\")**\n - Read `.specify/memory/constitution.md` for constraints/principles.\n - Load current `spec.md` / `plan.md` / `tasks.md` context if present.\n\n3. **Load Command Dependencies**\n - Match current command to required skills.\n - Load complementary superpowers skills.\n\n4. **Initialize Progress Tracking**\n - Create TodoWrite items for workflow phases.\n - Track completion status.\n\n### Command-Skill"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-spec-kit-speckit-orchestrator\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787750594767\n}"},{"path":"modules/artifact-structure.md","content":"---\nname: artifact-structure\ndescription: Documentation of spec-kit artifact structure, purposes, and organization\ncategory: reference\ntags: [artifacts, structure, organization, documentation]\ndependencies: [speckit-orchestrator]\ncomplexity: beginner\nestimated_tokens: 800\n---\n\n# Spec-Kit Artifact Structure\n\n## Overview\n\nSpec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.\n\n## Directory Structure\n\n```\nproject-root/\n├── .specify/ # Spec-kit infrastructure\n│ ├── scripts/ # Workflow automation scripts\n│ ├── templates/ # Artifact templates\n│ └── memory/ # Project context and constitution\n│\n└── specs/ # Feature specifications\n └── {N}-{short-name}/ # Feature directory\n ├── spec.md # What & Why (user-focused)\n ├── plan.md # How (technical design)\n ├── tasks.md # Implementation tasks\n ├── checklists/ # Quality validation checklists\n │ ├── requirements.md # Spec quality validation\n │ ├── ux.md # UX requirements validation\n │ ├── api.md # API requirements validation\n │ └── security.md # Security requirements validation\n ├── research.md # Technical research & decisions\n ├── data-model.md # Entity definitions\n ├── quickstart.md # Test scenarios\n └── contracts/ # API contracts\n ├── openapi.yaml\n └── graphql/\n```\n\n> **Note: Claude Code Plan Mode Namespace**\n>\n> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the\n> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.\n> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid\n> collision. When searching for scope artifacts:\n> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)\n> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)\n>\n> The two systems are complementary: Claude Plan Mode is for exploratory planning,\n> while spec-kit plans are structured implementation blueprints.\n\n## Core Artifacts\n\n### spec.md - Feature Specification\n\n**Purpose**: Define WHAT users need and WHY, without implementation details.\n\n**Audience**: Business stakeholders, product managers, non-technical reviewers.\n\n**Structure**:\n```markdown\n# Feature Name\n\n## Overview\n- Problem statement\n- User value proposition\n\n## User Scenarios\n- Who uses it\n- Primary flows\n- User goals\n\n## Functional Requirements\n- What must it do (testable)\n- Acceptance criteria\n\n## Success Criteria\n- Measurable outcomes\n- Technology-agnostic metrics\n- User-facing goals\n\n## Success Criteria (Optional)\n- Performance expectations\n- Security considerations\n- Accessibility needs\n\n## Edge Cases (Optional)\n- Boundary conditions\n- Err"},{"path":"modules/command-skill-matrix.md","content":"# Command-Skill Matrix\n\n## Overview\n\nThe Command-Skill Matrix defines which skills are required for each speckit command, ensuring proper dependencies are loaded and coordinated throughout the workflow.\n\n## Complete Mapping\n\n### Specification Phase\n\n**`/speckit-specify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: At command start, before any specification work\n- **Purpose**: Create or refine feature specifications with collaborative ideation\n\n**`/speckit-clarify`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: `superpowers:brainstorming`\n- **Loading Order**: brainstorming → spec-writing\n- **When to Load**: When specification needs refinement or has gaps\n- **Purpose**: Identify underspecified areas and encode clarifications\n\n**`/speckit-constitution`**\n- **Primary Skill**: `spec-writing`\n- **Complementary Skills**: None required\n- **Loading Order**: spec-writing only\n- **When to Load**: Creating or updating project principles\n- **Purpose**: Establish project governance and design principles\n\n### Planning Phase\n\n**`/speckit-plan`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:writing-plans`\n- **Loading Order**: task-planning → writing-plans\n- **When to Load**: After specification is complete\n- **Purpose**: Generate detailed implementation design artifacts\n\n**`/speckit-tasks`**\n- **Primary Skill**: `task-planning`\n- **Complementary Skills**: `superpowers:executing-plans`\n- **Loading Order**: task-planning → executing-plans\n- **When to Load**: After planning artifacts exist\n- **Purpose**: Generate dependency-ordered implementation tasks\n\n### Implementation Phase\n\n**`/speckit-implement`**\n- **Primary Skill**: None (uses loaded plan)\n- **Complementary Skills**: `superpowers:executing-plans`, `superpowers:systematic-debugging`\n- **Loading Order**: executing-plans → systematic-debugging (on-demand)\n- **When to Load**: When executing tasks from tasks.md\n- **Purpose**: Execute implementation tasks with error handling\n\n### Verification Phase\n\n**`/speckit-analyze`**\n- **Primary Skill**: None (analysis only)\n- **Complementary Skills**: `superpowers:systematic-debugging`, `superpowers:verification-before-completion`\n- **Loading Order**: Load both at analysis start\n- **When to Load**: After task generation or implementation\n- **Purpose**: Cross-artifact consistency and quality analysis\n\n**`/speckit-checklist`**\n- **Primary Skill**: None (generation only)\n- **Complementary Skills**: `superpowers:verification-before-completion`\n- **Loading Order**: verification-before-completion only\n- **When to Load**: When generating feature-specific checklists\n- **Purpose**: Create custom verification checklists\n\n**`/speckit-startup`**\n- **Primary Skill**: None (bootstrap only)\n- **Complementary Skills**: None required\n- **Loading Order**: N/A\n- **When to Load**: Session initialization\n- **Purpose**: Bootstra"},{"path":"modules/progress-tracking.md","content":"# Progress Tracking\n\n## Overview\n\nDefines TodoWrite item patterns and progress tracking strategies for speckit workflows. validates consistent status reporting and verification throughout all workflow phases.\n\n## TodoWrite Item Patterns\n\n### Universal Workflow Items\n\nFor every speckit command session:\n\n```\n- [ ] Verify repository context and .specify/ structure\n- [ ] Validate prerequisites (scripts, dependencies, templates)\n- [ ] Load command-specific skills\n- [ ] Execute command workflow\n- [ ] Verify artifacts created/updated\n- [ ] Complete progress tracking\n```\n\n### Specification Phase Items\n\n**`/speckit-specify`**\n```\n- [ ] Load spec-writing and brainstorming skills\n- [ ] Analyze feature description and requirements\n- [ ] Generate/update spec.md with template\n- [ ] Verify spec.md contains all required sections\n- [ ] Validate frontmatter metadata\n```\n\n**`/speckit-clarify`**\n```\n- [ ] Read existing spec.md\n- [ ] Identify underspecified areas\n- [ ] Ask targeted clarification questions (max 5)\n- [ ] Encode answers back into spec.md\n- [ ] Verify improved specification completeness\n```\n\n**`/speckit-constitution`**\n```\n- [ ] Gather project principles (interactive or provided)\n- [ ] Create/update constitution.md\n- [ ] Sync dependent templates with constitution\n- [ ] Verify template consistency\n```\n\n### Planning Phase Items\n\n**`/speckit-plan`**\n```\n- [ ] Load task-planning and writing-plans skills\n- [ ] Read spec.md and constitution.md\n- [ ] Execute planning template workflow\n- [ ] Generate plan.md with design artifacts\n- [ ] Verify plan completeness and consistency\n```\n\n**`/speckit-tasks`**\n```\n- [ ] Read all available design artifacts (spec, plan, constitution)\n- [ ] Analyze dependencies and ordering constraints\n- [ ] Generate tasks.md with concrete tasks\n- [ ] Verify task ordering and completeness\n- [ ] Mark tasks ready for implementation\n```\n\n### Implementation Phase Items\n\n**`/speckit-implement`**\n```\n- [ ] Load executing-plans skill\n- [ ] Read and parse tasks.md\n- [ ] Execute tasks in dependency order\n- [ ] Track completion status per task\n- [ ] Handle errors with systematic-debugging\n- [ ] Verify all tasks completed successfully\n```\n\n### Verification Phase Items\n\n**`/speckit-analyze`**\n```\n- [ ] Read spec.md, plan.md, tasks.md\n- [ ] Check cross-artifact consistency\n- [ ] Identify quality issues\n- [ ] Generate analysis report\n- [ ] Provide concrete recommendations with evidence\n```\n\n**`/speckit-checklist`**\n```\n- [ ] Read feature requirements from spec.md\n- [ ] Generate custom verification checklist\n- [ ] Output checklist in markdown format\n- [ ] Verify checklist completeness\n```\n\n## Workflow Phase Tracking\n\n### Phase States\n\n1. **Not Started**: Prerequisites not yet validated\n2. **In Progress**: Command executing, artifacts being created\n3. **Blocked**: Waiting for user input or error resolution\n4. **Completed**: Artifacts created, verification passed\n5. **Failed**: Unrecoverable error, manual intervention needed\n\n### Phase Transitions\n\n```\nNot "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Skill: speckit-orchestrator Owner: athola Summary: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:23:14.767Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:43:01.385Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:59:51.620Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:07:14.088Z | user Release v1.9.14 v1.9.13 | 2026-06-2","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1158,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T04:27:51.024Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T08:48:12.255Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}