[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77NF021PX3RPNRC5YJFVPVX":3,"skill-same:01M77NF021PX3RPNRC5YJFVPVX":229},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77NF021PX3RPNRC5YJFVPVX","superspec",null,"Orchestrates specification-driven development by combining spec-kit project governance (constitution, specs, plans, tasks) with obra\u002Fsuperpowers capabilities (brainstorming, writing-plans, TDD, subagent-driven-development, code-review). Use when the user wants to create project constitutions, write feature specifications, brainstorm edge cases, plan implementations, decompose tasks, execute with TDD discipline, or request code reviews within a structured development workflow.","milos85vasic\u002Fvasic","milos85vasic","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1803597?v=4","01M77NANGVP1VVX04JSJM4KSBD","Милош Васић 🇷🇸 🇷🇺","01M77NANHF239MM51N0127RBP3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: superspec\ndescription: >-\n  Orchestrates specification-driven development by combining spec-kit project\n  governance (constitution, specs, plans, tasks) with obra\u002Fsuperpowers\n  capabilities (brainstorming, writing-plans, TDD, subagent-driven-development,\n  code-review). Use when the user wants to create project constitutions, write\n  feature specifications, brainstorm edge cases, plan implementations, decompose\n  tasks, execute with TDD discipline, or request code reviews within a structured\n  development workflow.\ndescription_zh: >-\n  通过结合 spec-kit 项目治理（宪章、规格、计划、任务）与 obra\u002Fsuperpowers 能力\n  （头脑风暴、计划编写、TDD、子代理驱动开发、代码审查）来编排规格驱动开发。\n  当用户需要创建项目宪章、编写功能规格、头脑风暴边界情况、规划实现方案、\n  拆解任务、以 TDD 纪律执行开发或请求代码审查时使用。\n---\n\n# Superspec\n\nSuperspec unifies [spec-kit](https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit) specification-driven\ndevelopment with [obra\u002Fsuperpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers) agent\ncapabilities into a single workflow. Spec-kit provides the document structure and\ngovernance; superpowers provides deep clarification, task decomposition, and\nengineering execution discipline.\n\n![AI-Powered: End-to-End Development Workflow (SDD)](assets\u002Fworkflow-overview-en.png)\n\n## Prerequisites\n\n**Required**: None. Superspec works standalone with built-in fallback protocols.\n\n**Optional (enhanced)**: Install [obra\u002Fsuperpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers)\nskills to `~\u002F.agents\u002Fskills\u002F` or `.agents\u002Fskills\u002F` for richer brainstorming,\nplanning, and execution capabilities. See [superpowers-bridge.md](references\u002Fsuperpowers-bridge.md)\nfor detection and integration details.\n\n## Project Structure\n\nWhen initialized, superspec relies on spec-kit's two top-level directories\nat the project root: `.specify\u002F` for tool metadata and `specs\u002F` for feature\nartifacts.\n\n```\nyour-project\u002F\n├── .specify\u002F\n│   ├── memory\u002F\n│   │   └── constitution.md      # Project governance principles\n│   ├── superpowers.yml          # Superpowers detection status (auto-managed)\n│   └── templates\u002F               # Document templates (copied on init)\n└── specs\u002F\n    └── NNN-feature-name\u002F\n        ├── spec.md              # Feature specification\n        ├── plan.md              # Implementation plan\n        ├── tasks.md             # Task breakdown\n        ├── progress.yml         # Phase progress tracker (auto-managed)\n        └── checklist-*.md       # Generated checklists\n```\n\n## Commands\n\n| Command | Purpose |\n|---------|---------|\n| `\u002Fspeckit.superspec.status` | Show current progress and suggest next step (resumable) |\n| `\u002Fspeckit.constitution` | Create or update project governance principles |\n| `\u002Fspeckit.specify` | Create a feature specification with user stories |\n| `\u002Fspeckit.superspec.brainstorm` | Deep-dive edge cases and refine a spec document |\n| `\u002Fspeckit.plan` | Create a technical implementation plan |\n| `\u002Fspeckit.superspec.tasks` | Generate a phased task breakdown |\n| `\u002Fspeckit.superspec.execute` | Orchestrate implementation with TDD + subagents |\n| `\u002Fspeckit.superspec.review` | Run code review against spec requirements |\n| `\u002Fspeckit.checklist` | Generate a contextual checklist |\n\n---\n\n## Session Resumability\n\nSuperspec is designed to be **fully resumable across sessions**. All state is persisted\nin the `.specify\u002F` directory as markdown files. When a session is interrupted (agent\ntimeout, user leaves, CLI crash), no progress is lost.\n\n### Progress Tracking\n\nEach feature spec directory contains a `progress.yml` file that records phase status:\n\n```yaml\n# specs\u002FNNN-feature-name\u002Fprogress.yml\nfeature: feature-name\ncreated: 2026-04-22\ncurrent_phase: brainstorm\nphases:\n  constitution: { status: done, updated: 2026-04-22 }\n  specify:      { status: done, updated: 2026-04-22 }\n  brainstorm:   { status: in_progress, updated: 2026-04-22, sessions: 1 }\n  plan:         { status: pending }\n  tasks:        { status: pending }\n  execute:      { status: pending }\n  review:       { status: pending }\n```\n\n**Status values**: `pending`, `in_progress`, `done`, `skipped`\n\nEvery command updates `progress.yml` when it starts (`in_progress`) and finishes (`done`).\n\n### Superpowers Status Tracking\n\nA project-level file `.specify\u002Fsuperpowers.yml` records which superpowers skills\nare available. This makes the superpowers integration **visible in the project docs**\nand **persistent across sessions** — no need to re-detect on every command.\n\n```yaml\n# .specify\u002Fsuperpowers.yml\nlast_checked: 2026-04-22T14:30:00\nskills:\n  brainstorming:\n    detected: true\n    path: ~\u002F.agents\u002Fskills\u002Fbrainstorming\u002FSKILL.md\n  writing-plans:\n    detected: true\n    path: ~\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md\n  executing-plans:\n    detected: false\n  subagent-driven-development:\n    detected: false\n  test-driven-development:\n    detected: true\n    path: .agents\u002Fskills\u002Ftest-driven-development\u002FSKILL.md\n  requesting-code-review:\n    detected: false\n```\n\n**When this file is updated**:\n- On `\u002Fspeckit.constitution` (initial creation)\n- On `\u002Fspeckit.superspec.status` (re-check)\n- On any command that needs a superpowers skill (lazy re-check if missing)\n- User can manually edit this file to override detection results\n\n**Why persist this**: So that project documentation reflects which superpowers are\nin use. A new team member reading `.specify\u002F` can immediately see the project's\nenhanced capabilities without running any command.\n\n### Resume Protocol\n\nWhen ANY superspec command is invoked, the agent MUST first run the **resume check**:\n\n1. Check if `.specify\u002F` directory exists\n2. If yes, scan for `progress.yml` files in each spec directory\n3. Read the most recent `progress.yml` to determine `current_phase`\n4. Read `.specify\u002Fsuperpowers.yml` to determine which superpowers are available.\n   If the file does not exist, run superpowers detection and create it.\n5. Report to user: \"Detected existing progress for [feature]: [phase] is [status].\n   Superpowers: [list detected skills]. Resuming from this point.\" or\n   \"No previous progress found, starting fresh.\"\n6. For `in_progress` phases: re-read all existing artifacts for that phase and\n   continue where the agent left off (e.g., resume brainstorming from the last\n   logged session, resume execution from the first unchecked task)\n\n### How Each Phase Resumes\n\n| Phase | Resume Signal | Resume Behavior |\n|-------|---------------|-----------------|\n| `constitution` | `constitution.md` exists but incomplete | Re-read and ask about missing sections |\n| `specify` | `spec.md` exists with `[NEEDS CLARIFICATION]` markers | Continue interview for unresolved items |\n| `brainstorm` | `Brainstorm Log` has entries, `Open Questions` has `Open` items | Skip already-explored categories, continue from open questions |\n| `plan` | `plan.md` exists with `NEEDS CLARIFICATION` fields | Fill in missing technical context |\n| `tasks` | `tasks.md` exists | Verify completeness, add missing tasks |\n| `execute` | `tasks.md` has mix of `[x]` and `[ ]` checkboxes | Skip completed tasks, resume from first unchecked task in current phase |\n| `review` | Review checklist partially completed | Continue from unchecked review items |\n\n---\n\n## `\u002Fspeckit.superspec.status`\n\n**Input**: Optional spec number or \"all\" via `$ARGUMENTS`. Defaults to showing all features.\n**Output**: Progress report printed to user.\n\n**Process**:\n1. Scan `.specify\u002F` directory structure\n2. Check if `constitution.md` exists\n3. **Run superpowers detection**: Check for all superpowers skills at\n   `.agents\u002Fskills\u002F` and `~\u002F.agents\u002Fskills\u002F`. Update `.specify\u002Fsuperpowers.yml`\n   with current detection results.\n4. For each spec directory, read `progress.yml` (or infer progress from existing files)\n5. Display a status summary:\n\n```\nSuperspec Project Status\n========================\nConstitution: Done (2026-04-22)\nSuperpowers:  brainstorming (detected), writing-plans (not found)\n\nFeatures:\n  001-user-auth    [####------] execute (Phase 5\u002F6) — T012\u002FT019 tasks done\n  002-photo-upload [##--------] brainstorm (Phase 2\u002F6) — 2 open questions\n  003-settings     [#---------] specify (Phase 1\u002F6) — draft\n\nSuggested next step: \u002Fspeckit.superspec.execute 001\n```\n\n5. If no `.specify\u002F` exists, suggest: \"No superspec project found. Run\n   `\u002Fspeckit.constitution` to get started.\"\n\n**File inference fallback**: If `progress.yml` does not exist, infer progress from\nwhich files are present:\n- `spec.md` exists → specify is done\n- `spec.md` has Brainstorm Log entries → brainstorm was run\n- `plan.md` exists → plan is done\n- `tasks.md` exists → tasks are done\n- `tasks.md` has `[x]` checkboxes → execute is in progress (count checked vs total)\n\n---\n\n## `\u002Fspeckit.constitution`\n\n**Input**: Project name and optional description via `$ARGUMENTS`.\n**Output**: `.specify\u002Fmemory\u002Fconstitution.md`\n\n**Process**:\n1. Create `.specify\u002F` directory structure if it does not exist\n2. Copy all files from this skill's `templates\u002F` directory into `.specify\u002Ftemplates\u002F`\n3. Read the template at `.specify\u002Ftemplates\u002Fconstitution-template.md`\n4. Interview the user about core principles, technology stack, design system, quality gates\n5. Generate `constitution.md` from template, filling in user responses\n6. Write to `.specify\u002Fmemory\u002Fconstitution.md`\n\n**Gate**: Constitution must exist before any other command can run.\n\n---\n\n## `\u002Fspeckit.specify`\n\n**Input**: Feature name and description via `$ARGUMENTS`.\n**Output**: `specs\u002FNNN-feature-name\u002Fspec.md`\n\n**Process**:\n1. Verify `.specify\u002Fmemory\u002Fconstitution.md` exists (abort with guidance if not)\n2. Determine the next spec number NNN (scan existing `specs\u002F` directories)\n3. Read the template at `.specify\u002Ftemplates\u002Fspec-template.md`\n4. Read the constitution to understand project principles and constraints\n5. Interview the user about user scenarios, requirements, success criteria\n6. Generate `spec.md` from template with user responses\n7. Write to `specs\u002FNNN-feature-name\u002Fspec.md`\n\n**Next step suggestion**: Run `\u002Fspeckit.superspec.brainstorm` on the new spec to discover edge cases.\n\n---\n\n## `\u002Fspeckit.superspec.brainstorm`\n\n**Input**: Path to a spec file (e.g., `specs\u002F001-auth\u002Fspec.md`) and an optional\nfocus topic via `$ARGUMENTS`.\n**Output**: Updated spec file with refined edge cases, resolved open questions, and\nbrainstorm log entries.\n\n**Process**:\n1. Read the target spec file\n2. Read the constitution for project constraints\n3. **Superpowers detection**: Check for `brainstorming` skill (see [superpowers-bridge.md](references\u002Fsuperpowers-bridge.md))\n   - **If found**: Read the brainstorming SKILL.md and follow its questioning protocol,\n     adapting all outputs to the target spec file\n   - **If not found**: Use the built-in questioning protocol (see [workflow-guide.md](references\u002Fworkflow-guide.md) Phase 2)\n4. Ask questions **one at a time**, focusing on:\n   - Boundary conditions and edge cases\n   - Error scenarios and failure modes\n   - Scale and performance implications\n   - Security and privacy concerns\n   - User confusion and UX pitfalls\n5. After each answer, update the spec's \"Open Questions\" section (mark resolved items)\n6. When the user confirms the spec is ready, update the \"Brainstorm Log\" with a\n   dated summary of insights discovered\n\n**Iteration**: This command can be run multiple times on the same spec. Each session\nappends to the brainstorm log.\n\n---\n\n## `\u002Fspeckit.plan`\n\n**Input**: Optional spec number or path via `$ARGUMENTS`. Defaults to the latest spec.\n**Output**: `specs\u002FNNN-feature-name\u002Fplan.md`\n\n**Process**:\n1. Read the target spec file and constitution\n2. Read the template at `.specify\u002Ftemplates\u002Fplan-template.md`\n3. Perform a **constitution check** — verify the plan aligns with all governance principles\n4. Research the codebase to determine technical context (language, dependencies, storage,\n   testing framework, project type)\n5. Design the project structure and identify files to create or modify\n6. Determine the **execution strategy**: which tasks need TDD, which support parallel\n   subagent execution, where human checkpoints are needed\n7. Generate `plan.md` from template\n8. Write to `specs\u002FNNN-feature-name\u002Fplan.md`\n\n**Superpowers bridge**: If `writing-plans` skill is detected, read it and use its\nblueprint generation process to enhance the plan's task structure section. See\n[superpowers-bridge.md](references\u002Fsuperpowers-bridge.md).\n\n---\n\n## `\u002Fspeckit.superspec.tasks`\n\n**Input**: Optional spec number or path via `$ARGUMENTS`. Defaults to the latest spec.\n**Output**: `specs\u002FNNN-feature-name\u002Ftasks.md`\n\n**Process**:\n1. Read the spec, plan, and constitution for the target feature\n2. Read the template at `.specify\u002Ftemplates\u002Ftasks-template.md`\n3. **Superpowers detection**: Check for `writing-plans` skill\n   - **If found**: Read the writing-plans SKILL.md and follow its task decomposition\n     process, adapting outputs to the tasks template structure\n   - **If not found**: Decompose directly from the plan using the template\n4. Organize tasks by phase: Setup → Foundational → User Stories (by priority) → Polish\n5. Apply execution markers to each task:\n   - `[P]` — can run in parallel (different files, no dependencies)\n   - `[TDD]` — must follow RED-GREEN-REFACTOR discipline\n   - `[REVIEW]` — requires code review before proceeding\n   - `[SUBAGENT]` — can be delegated to a subagent\n6. Define phase dependencies and checkpoint gates\n7. Write to `specs\u002FNNN-feature-name\u002Ftasks.md`\n\n---\n\n## `\u002Fspeckit.superspec.execute`\n\n**Input**: Optional spec number or path via `$ARGUMENTS`. Defaults to the latest spec.\n**Output**: Code changes in the project, updated task checkboxes.\n\n**Process**:\n1. Read the tasks file for the target feature\n2. Read the plan and constitution for context\n3. **Superpowers detection**: Check for `executing-plans`, `subagent-driven-development`,\n   and `test-driven-development` skills\n4. Walk through tasks phase by phase:\n   - **`[TDD]` tasks**: If TDD skill found, follow its RED-GREEN-REFACTOR process.\n     Otherwise: write test → verify it fails → implement → verify it passes\n   - **`[SUBAGENT]` tasks**: If subagent-driven-development skill found, follow its\n     dispatch protocol. Otherwise: implement sequentially in-session\n   - **`[P]` tasks**: Launch parallel tasks where possible using the Task tool\n   - **`[REVIEW]` tasks**: Pause and run review protocol (see `\u002Fspeckit.superspec.review`)\n5. At each **phase checkpoint**: Summarize completed work, run tests if applicable,\n   ask user for approval before proceeding to next phase\n6. Update task checkboxes in `tasks.md` as each task completes\n\n**Human checkpoints**: The agent MUST pause at every phase boundary and wait for\nexplicit user approval. Never skip a checkpoint.\n\n---\n\n## `\u002Fspeckit.superspec.review`\n\n**Input**: Optional scope (file paths or \"all changes\") via `$ARGUMENTS`.\n**Output**: Review findings reported to user, optionally written to a checklist file.\n\n**Process**:\n1. Read the spec and plan for the feature being reviewed\n2. **Superpowers detection**: Check for `requesting-code-review` skill\n   - **If found**: Read the skill and follow its pre-evaluation checklist and review\n     dispatch protocol\n   - **If not found**: Use the built-in review protocol below\n3. Built-in review protocol:\n   - **Spec compliance**: Verify each acceptance scenario from the spec is implemented\n   - **Edge case coverage**: Verify brainstormed edge cases are handled\n   - **Constitution compliance**: Check all governance principles are respected\n   - **Code quality**: Check for bugs, security issues, error handling\n   - **Test coverage**: Verify tests exist for critical paths\n4. Report findings with confidence scores (0-100, only report issues >= 80)\n5. Group findings by severity: Critical > Important > Suggestion\n\n---\n\n## `\u002Fspeckit.checklist`\n\n**Input**: Checklist type and optional context via `$ARGUMENTS`.\n**Output**: `specs\u002FNNN-feature-name\u002Fchecklist-{type}.md`\n\n**Process**:\n1. Read the template at `.specify\u002Ftemplates\u002Fchecklist-template.md`\n2. Read the spec, plan, and tasks for context\n3. Generate a checklist appropriate to the requested type (e.g., \"launch readiness\",\n   \"security audit\", \"accessibility review\", \"code review\")\n4. Write to `specs\u002FNNN-feature-name\u002Fchecklist-{type}.md`\n\n---\n\n## Unified Workflow\n\nThe recommended end-to-end workflow:\n\n```\nPhase 0: \u002Fspeckit.constitution     → Establish project governance\nPhase 1: \u002Fspeckit.specify          → Define feature requirements\nPhase 2: \u002Fspeckit.superspec.brainstorm       → Clarify edge cases (iterate)\nPhase 3: \u002Fspeckit.plan             → Design technical approach\nPhase 4: \u002Fspeckit.superspec.tasks            → Decompose into executable tasks\nPhase 5: \u002Fspeckit.superspec.execute          → Implement with TDD + subagents\nPhase 6: \u002Fspeckit.superspec.review           → Verify against spec\n```\n\nEach phase has an explicit **gate** — the agent verifies prerequisites before proceeding.\nRun `\u002Fspeckit.superspec.brainstorm` multiple times until the spec is solid. The user controls\nwhen to advance to the next phase.\n\n## Additional Resources\n\n- Detailed phase-by-phase guide: [workflow-guide.md](references\u002Fworkflow-guide.md)\n- Superpowers integration details: [superpowers-bridge.md](references\u002Fsuperpowers-bridge.md)\n- End-to-end example: [sample-workflow.md](examples\u002Fsample-workflow.md)\n","# Superspec\n\nSuperspec unifies [spec-kit](https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit) specification-driven\ndevelopment with [obra\u002Fsuperpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers) agent\ncapabilities into a single workflow. Spec-kit provides the document structure and\ngovernance; superpowers provides deep clarification, task decomposition, and\nengineering execution discipline.\n\n![AI-Powered: End-to-End Development Workflow (SDD)](assets\u002Fworkflow-overview-en.png)\n\n## Prerequisites\n\n**Required**: None. Superspec works standalone with built-in fallback protocols.\n\n**Optional (enhanced)**: Install [obra\u002Fsuperpowers](https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers)\nskills to `~\u002F.agents\u002Fskills\u002F` or `.agents\u002Fskills\u002F` for richer brainstorming,\nplanning, and execution capabilities. See [superpowers-bridge.md](references\u002Fsuperpowers-bridge.md)\nfor detection and integration details.\n\n## Project Structure\n\nWhen initialized, superspec relies on spec-kit's two top-level directories\nat the project root: `.specify\u002F` for tool metadata and `specs\u002F` for feature\nartifacts.\n\n```\nyour-project\u002F\n├── .specify\u002F\n│   ├── memory\u002F\n│   │   └── constitution.md      # Project governance principles\n│   ├── superpowers.yml          # Superpowers detection status (auto-managed)\n│   └── templates\u002F               # Document templates (copied on init)\n└── specs\u002F\n    └── NNN-feature-name\u002F\n        ├── spec.md              # Feature specification\n        ├── plan.md              # Implementation plan\n        ├── tasks.md             # Task breakdown\n        ├── progress.yml         # Phase progress tracker (auto-managed)\n        └── checklist-*.md       # Generated checklists\n```\n\n## Commands\n\n| Command | Purpose |\n|---------|---------|\n| `\u002Fspeckit.superspec.status` | Show current progress and suggest next step (resumable) |\n| `\u002Fspeckit.constitution` | Create or update project governance principles |\n| `\u002Fspeckit.specify` | Create a feature specification with user stories |\n| `\u002Fspeckit.superspec.brainstorm` | Deep-dive edge cases and refine a spec document |\n| `\u002Fspeckit.plan` | Create a technical implementation plan |\n| `\u002Fspeckit.superspec.tasks` | Generate a phased task breakdown |\n| `\u002Fspeckit.superspec.execute` | Orchestrate implementation with TDD + subagents |\n| `\u002Fspeckit.superspec.review` | Run code review against spec requirements |\n| `\u002Fspeckit.checklist` | Generate a contextual checklist |\n\n---\n\n## Session Resumability\n\nSuperspec is designed to be **fully resumable across sessions**. All state is persisted\nin the `.specify\u002F` directory as markdown files. When a session is interrupted (agent\ntimeout, user leaves, CLI crash), no progress is lost.\n\n### Progress Tracking\n\nEach feature spec directory contains a `progress.yml` file that records phase status:\n\n```yaml\n# specs\u002FNNN-feature-name\u002Fprogress.yml\nfeature: feature-name\ncreated: 2026-04-22\ncurrent_phase: brainstorm\nphases:\n  constitution: { status: done, updated: 2026-04-22 }\n  specify:      { status: done, updated: 2026-04-22 }\n  brainstorm:   { status: in_progress, updated: 2026-04-22, sessions: 1 }\n  plan:         { status: pending }\n  tasks:        { status: pending }\n  execute:      { status: pending }\n  review:       { status: pending }\n```\n\n**Status values**: `pending`, `in_progress`, `done`, `skipped`\n\nEvery command updates `progress.yml` when it starts (`in_progress`) and finishes (`done`).\n\n### Superpowers Status Tracking\n\nA project-level file `.specify\u002Fsuperpowers.yml` records which superpowers skills\nare available. This makes the superpowers integration **visible in the project docs**\nand **persistent across sessions** — no need to re-detect on every command.\n\n```yaml\n# .specify\u002Fsuperpowers.yml\nlast_checked: 2026-04-22T14:30:00\nskills:\n  brainstorming:\n    detected: true\n    path: ~\u002F.agents\u002Fskills\u002Fbrainstorming\u002FSKILL.md\n  writing-plans:\n    detected: true\n    path: ~\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md\n  executing-plans:\n    detected: false\n  subagent-driven-development:\n    detected: false\n  test-driven-development:\n    detected: true\n    path: .agents\u002Fskills\u002Ftest-driven-development\u002FSKILL.md\n  requesting-code-review:\n    detected: false\n```\n\n**When this file is updated**:\n- On `\u002Fspeckit.constitution` (initial creation)\n- On `\u002Fspeckit.superspec.status` (re-check)\n- On any command that needs a superpowers skill (lazy re-check if missing)\n- User can manually edit this file to override detection results\n\n**Why persist this**: So that project documentation reflects which superpowers are\nin use. A new team member reading `.specify\u002F` can immediately see the project's\nenhanced capabilities without running any command.\n\n### Resume Protocol\n\nWhen ANY superspec command is invoked, the agent MUST first run the **resume check**:\n\n1. Check if `.specify\u002F` directory exists\n2. If yes, scan for `progress.yml` files in each spec directory\n3. Read the most recent `progress.yml` to determine `current_phase`\n4. Read `.specify\u002Fsuperpowers.yml` to determine which superpowers are available.\n   If the file does not exist, run superpowers detection and create it.\n5. Report to user: \"Detected existing progress for [feature]: [phase] is [status].\n   Superpowers: [list detected skills]. Resuming from this point.\" or\n   \"No previous progress found, starting fresh.\"\n6. For `in_progress` phases: re-read all existing artifacts for that phase and\n   continue where the agent left off (e.g., resume brainstorming from the last\n   logged session, resume execution from the first unchecked task)\n\n### How Each Phase Resumes\n\n| Phase | Resume Signal | Resume Behavior |\n|-------|---------------|-----------------|\n| `constitution` | `constitution.md` exists but incomplete | Re-read and ask about missing sections |\n| `specify` | `spec.md` exists with `[NEEDS CLARIFICATION]` markers | Continue interview for unresolved items |\n| `brainstorm` | `Brainstorm Log` has entries, `Open Questions` has `Open` items | Skip already-explored categories, continue from open questions |\n| `plan` | `plan.md` exists with `NEEDS CLARIFICATION` fields | Fill in missing technical context |\n| `tasks` | `tasks.md` exists | Verify completeness, add missing tasks |\n| `execute` | `tasks.md` has mix of `[x]` and `[ ]` checkboxes | Skip completed tasks, resume from first unchecked task in current phase |\n| `review` | Review checklist partially completed | Continue from unchecked review items |\n\n---\n\n## `\u002Fspeckit.superspec.status`\n\n**Input**: Optional spec number or \"all\" via `$ARGUMENTS`. Defaults to showing all features.\n**Output**: Progress report printed to user.\n\n**Process**:\n1. Scan `.specify\u002F` directory structure\n2. Check if `constitution.md` exists\n3. **Run superpowers detection**: Check for all superpowers skills at\n   `.agents\u002Fskills\u002F` and `~\u002F.agents\u002Fskills\u002F`. Update `.specify\u002Fsuperpowers.yml`\n   with current detection results.\n4. For each spec directory, read `progress.yml` (or infer progress from existing files)\n5. Display a status summary:\n\n```\nSuperspec Project Status\n========================\nConstitution: Done (2026-04-22)\nSuperpowers:  brainstorming (detected), writing-plans (not found)\n\nFeatures:\n  001-user-auth    [####------] execute (Phase 5\u002F6) — T012\u002FT019 tasks done\n  002-photo-upload [##--------] brainstorm (Phase 2\u002F6) — 2 open questions\n  003-settings     [#---------] specify (Phase 1\u002F6) — draft\n\nSuggested next step: \u002Fspeckit.superspec.execute 001\n```\n\n5. If no `.specify\u002F` exists, suggest: \"No superspec project found. Run\n   `\u002Fspeckit.constitution` to get started.\"\n\n**File inference fallback**: If `progress.yml` does not exist, infer progress from\nwhich files are present:\n- `spec.md` exists → specify is done\n- `spec.md` has Brainstorm Log entries → brainstorm was run\n- `plan.md` exists → plan is done\n- `tasks.md` exists → tasks are done\n- `tasks.md` has `[x]` checkboxes → execute is in progress (count checked vs total)\n\n---\n\n## `\u002Fspeckit.constitution`\n\n**Input**: Project name and optional description via `$ARGUMENTS`.\n**Output**: `.specify\u002Fmemory\u002Fconstitution.md`\n\n**Process**:\n1. Create `.specify\u002F` directory structure if it does not exist\n2. Copy all files from this skill's `templates\u002F` directory into `.specify\u002Ftemplates\u002F`\n3. Read the template at `.specify\u002Ftemplates\u002Fconstitution-template.md`\n4. Interview the user about core principles, technology stack, design system, quality gates\n5. Generate `constitution.md` from template, filling in user responses\n6. Write to `.specify\u002Fmemory\u002Fconstitution.md`\n\n**Gate**: Constitution must exist before any other command can run.\n\n---\n\n## `\u002Fspeckit.specify`\n\n**Input**: Feature name and description via `$ARGUMENTS`.\n**Output**: `specs\u002FNNN-feature-name\u002Fspec.md`\n\n**Process**:\n1. Verify `.specify\u002Fmemory\u002Fconstitution.md` exists (abort with guidance if not)\n2. Determine the next spec number NNN (scan existing `specs\u002F` directories)\n3. Read the template at `.specify\u002Ftemplates\u002Fspec-template.md`\n4. Read the constitution to understand project principles and constraints\n5. Interview the user about user scenarios, requirements, success criteria\n6. Generate `spec.md` from template with user responses\n7. Write to `specs\u002FNNN-feature-name\u002Fspec.md`\n\n**Next step suggestion**: Run `\u002Fspeckit.superspec.brainstorm` on the new spec to discover edge cases.\n\n---\n\n## `\u002Fspeckit.superspec.brainstorm`\n\n**Input**: Path to a spec file (e.g., `specs\u002F001-auth\u002Fspec.md`) and an optional\nfocus topic via `$ARGUMENTS`.\n**Output**: Updated spec file with refined edge cases, resolved open questions, and\nbrainstorm log entries.\n\n**Process**:\n1. Read the target spec file\n2. Read the constitution for project constraints\n3. **Superpowers detection**: Check for `brainstorming` skill (see [superpowers-bridge.md](references\u002Fsuperpowers-bridge.md))\n   - **If found**: Read the brainstorming SKILL.md and follow its questioning protocol,\n     adapting all outputs to the target spec file\n   - **If not found**: Use the built-in questioning protocol (see [workflow-guide.md](references\u002Fworkflow-guide.md) Phase 2)\n4. Ask questions **one at a time**, focusing on:\n   - Boundary conditions and edge cases\n   - Error scenarios and failure modes\n   - Scale and performance implications\n   - Security and privacy concerns\n   - User confusion and UX pitfalls\n5. After each answer, update the spec's \"Open Questions\" section (mark resolved items)\n6. When the user confirms the spec is ready, update the \"Brainstorm Log\" with a\n   dated summary of insights discovered\n\n**Iteration**: This command can be run multiple times on the same spec. Each session\nappends to the brainstorm log.\n\n---\n\n## `\u002Fspeckit.plan`\n\n**Input**: Optional spec number or path via `$ARGUMENTS`. Defaults to the latest spec.\n**Output**: `specs\u002FNNN-feature-name\u002Fplan.md`\n\n**Process**:\n1. Read the target spec file and constitution\n2. Read the template at `.specify\u002Ftemplates\u002Fplan-template.md`\n3. Perform a **constitution check** — verify the plan aligns with all governance principles\n4. Research the codebase to determine technical context (language, dependencies, storage,\n   testing framework, project type)\n5. Design the project structure and identify files to create or modify\n6. Determine the **execution strategy**: which tasks need TDD, which support parallel\n   subagent execution, where human checkpoints are needed\n7. Generate `plan.md` from template\n8. Write to `specs\u002FNNN-feature-name\u002Fplan.md`\n\n**Superpowers bridge**: If `writing-plans` skill is detected, read it and use its\nblueprint generation process to enhance the plan's task structure section. See\n[superpowers-bridge.md](references\u002Fsuperpowers-bridge.md).\n\n---\n\n## `\u002Fspeckit.superspec.tasks`\n\n**Input**: Optional spec number or path via `$ARGUMENTS`. Defaults to the latest spec.\n**Output**: `specs\u002FNNN-feature-name\u002Ftasks.md`\n\n**Process**:\n1. Read the spec, plan, and constitution for the target feature\n2. Read the template at `.specify\u002Ftemplates\u002Ftasks-template.md`\n3. **Superpowers detection**: Check for `writing-plans` skill\n   - **If found**: Read the writing-plans SKILL.md and follow its task decomposition\n     process, adapting outputs to the tasks template structure\n   - **If not found**: Decompose directly from the plan using the template\n4. Organize tasks by phase: Setup → Foundational → User Stories (by priority) → Polish\n5. Apply execution markers to each task:\n   - `[P]` — can run in parallel (different files, no dependencies)\n   - `[TDD]` — must follow RED-GREEN-REFACTOR discipline\n   - `[REVIEW]` — requires code review before proceeding\n   - `[SUBAGENT]` — can be delegated to a subagent\n6. Define phase dependencies and checkpoint gates\n7. Write to `specs\u002FNNN-feature-name\u002Ftasks.md`\n\n---\n\n## `\u002Fspeckit.superspec.execute`\n\n**Input**: Optional spec number or path via `$ARGUMENTS`. Defaults to the latest spec.\n**Output**: Code changes in the project, updated task checkboxes.\n\n**Process**:\n1. Read the tasks file for the target feature\n2. Read the plan and constitution for context\n3. **Superpowers detection**: Check for `executing-plans`, `subagent-driven-development`,\n   and `test-driven-development` skills\n4. Walk through tasks phase by phase:\n   - **`[TDD]` tasks**: If TDD skill found, follow its RED-GREEN-REFACTOR process.\n     Otherwise: write test → verify it fails → implement → verify it passes\n   - **`[SUBAGENT]` tasks**: If subagent-driven-development skill found, follow its\n     dispatch protocol. Otherwise: implement sequentially in-session\n   - **`[P]` tasks**: Launch parallel tasks where possible using the Task tool\n   - **`[REVIEW]` tasks**: Pause and run review protocol (see `\u002Fspeckit.superspec.review`)\n5. At each **phase checkpoint**: Summarize completed work, run tests if applicable,\n   ask user for approval before proceeding to next phase\n6. Update task checkboxes in `tasks.md` as each task completes\n\n**Human checkpoints**: The agent MUST pause at every phase boundary and wait for\nexplicit user approval. Never skip a checkpoint.\n\n---\n\n## `\u002Fspeckit.superspec.review`\n\n**Input**: Optional scope (file paths or \"all changes\") via `$ARGUMENTS`.\n**Output**: Review findings reported to user, optionally written to a checklist file.\n\n**Process**:\n1. Read the spec and plan for the feature being reviewed\n2. **Superpowers detection**: Check for `requesting-code-review` skill\n   - **If found**: Read the skill and follow its pre-evaluation checklist and review\n     dispatch protocol\n   - **If not found**: Use the built-in review protocol below\n3. Built-in review protocol:\n   - **Spec compliance**: Verify each acceptance scenario from the spec is implemented\n   - **Edge case coverage**: Verify brainstormed edge cases are handled\n   - **Constitution compliance**: Check all governance principles are respected\n   - **Code quality**: Check for bugs, security issues, error handling\n   - **Test coverage**: Verify tests exist for critical paths\n4. Report findings with confidence scores (0-100, only report issues >= 80)\n5. Group findings by severity: Critical > Important > Suggestion\n\n---\n\n## `\u002Fspeckit.checklist`\n\n**Input**: Checklist type and optional context via `$ARGUMENTS`.\n**Output**: `specs\u002FNNN-feature-name\u002Fchecklist-{type}.md`\n\n**Process**:\n1. Read the template at `.specify\u002Ftemplates\u002Fchecklist-template.md`\n2. Read the spec, plan, and tasks for context\n3. Generate a checklist appropriate to the requested type (e.g., \"launch readiness\",\n   \"security audit\", \"accessibility review\", \"code review\")\n4. Write to `specs\u002FNNN-feature-name\u002Fchecklist-{type}.md`\n\n---\n\n## Unified Workflow\n\nThe recommended end-to-end workflow:\n\n```\nPhase 0: \u002Fspeckit.constitution     → Establish project governance\nPhase 1: \u002Fspeckit.specify          → Define feature requirements\nPhase 2: \u002Fspeckit.superspec.brainstorm       → Clarify edge cases (iterate)\nPhase 3: \u002Fspeckit.plan             → Design technical approach\nPhase 4: \u002Fspeckit.superspec.tasks            → Decompose into executable tasks\nPhase 5: \u002Fspeckit.superspec.execute          → Implement with TDD + subagents\nPhase 6: \u002Fspeckit.superspec.review           → Verify against spec\n```\n\nEach phase has an explicit **gate** — the agent verifies prerequisites before proceeding.\nRun `\u002Fspeckit.superspec.brainstorm` multiple times until the spec is solid. The user controls\nwhen to advance to the next phase.\n\n## Additional Resources\n\n- Detailed phase-by-phase guide: [workflow-guide.md](references\u002Fworkflow-guide.md)\n- Superpowers integration details: [superpowers-bridge.md](references\u002Fsuperpowers-bridge.md)\n- End-to-end example: [sample-workflow.md](examples\u002Fsample-workflow.md)\n",{"name":5,"description":7,"description_zh":25},"通过结合 spec-kit 项目治理（宪章、规格、计划、任务）与 obra\u002Fsuperpowers 能力 （头脑风暴、计划编写、TDD、子代理驱动开发、代码审查）来编排规格驱动开发。 当用户需要创建项目宪章、编写功能规格、头脑风暴边界情况、规划实现方案、 拆解任务、以 TDD 纪律执行开发或请求代码审查时使用。","main","0a218330c648d72c1be24266c913057dd03f441d",".specify\u002Fextensions\u002Fsuperspec",0,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic","https:\u002F\u002Fgithub.com\u002Fmilos85vasic","http:\u002F\u002Fwww.milosvasic.ru\u002F","Making programs and tools","2026-10-29 21:13:35",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add milos85vasic\u002Fvasic --skill superspec",{"tool":41,"command":42},"bunx","bunx skills add milos85vasic\u002Fvasic --skill superspec",{"tool":44,"command":45},"pnpm","pnpm dlx skills add milos85vasic\u002Fvasic --skill superspec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002FSKILL.md",true,[49,55,61,65,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139,143,147,151,155,159,163,167,171,175,179,183,187,191,197,201,205,209,213,217,221,225],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},".gitattributes","OTHER","其他",1881,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002F.gitattributes",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},".github\u002Fworkflows\u002Fci.yml","REFERENCE","参考文档",1657,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002F.github\u002Fworkflows\u002Fci.yml",{"path":62,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":63,"sourceHtmlUrl":64},".gitignore",247,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002F.gitignore",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Fworkflow-overview-en.png","ASSET","资产文件",12165872,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fassets\u002Fworkflow-overview-en.png",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Fworkflow-overview-zh.png",1945421,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fassets\u002Fworkflow-overview-zh.png",{"path":76,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":77,"sourceHtmlUrl":78},"CHANGELOG.md",3958,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002FCHANGELOG.md",{"path":80,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":81,"sourceHtmlUrl":82},"commands\u002Fbrainstorm.md",2015,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Fbrainstorm.md",{"path":84,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":85,"sourceHtmlUrl":86},"commands\u002Fexecute.md",1959,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Fexecute.md",{"path":88,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":89,"sourceHtmlUrl":90},"commands\u002Fhooks\u002Fafter-execute.md",752,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Fhooks\u002Fafter-execute.md",{"path":92,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":93,"sourceHtmlUrl":94},"commands\u002Fhooks\u002Fafter-tasks.md",731,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Fhooks\u002Fafter-tasks.md",{"path":96,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":97,"sourceHtmlUrl":98},"commands\u002Fhooks\u002Fbefore-execute.md",718,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Fhooks\u002Fbefore-execute.md",{"path":100,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":101,"sourceHtmlUrl":102},"commands\u002Freview.md",1771,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Freview.md",{"path":104,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":105,"sourceHtmlUrl":106},"commands\u002Fstatus.md",1799,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Fstatus.md",{"path":108,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":109,"sourceHtmlUrl":110},"commands\u002Ftasks.md",1890,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fcommands\u002Ftasks.md",{"path":112,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":113,"sourceHtmlUrl":114},"examples\u002Fsample-workflow.md",11371,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fsample-workflow.md",{"path":116,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":117,"sourceHtmlUrl":118},"examples\u002Fstatic-landing-page\u002F.specify\u002Fmemory\u002Fconstitution.md",6008,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002F.specify\u002Fmemory\u002Fconstitution.md",{"path":120,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":121,"sourceHtmlUrl":122},"examples\u002Fstatic-landing-page\u002FCLAUDE.md",227,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002FCLAUDE.md",{"path":124,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":125,"sourceHtmlUrl":126},"examples\u002Fstatic-landing-page\u002FREADME.md",4278,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002FREADME.md",{"path":128,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":129,"sourceHtmlUrl":130},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fchecklists\u002Frequirements.md",1307,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fchecklists\u002Frequirements.md",{"path":132,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":133,"sourceHtmlUrl":134},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fchecklists\u002Freview.md",14438,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fchecklists\u002Freview.md",{"path":136,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":137,"sourceHtmlUrl":138},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fdata-model.md",2533,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fdata-model.md",{"path":140,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":141,"sourceHtmlUrl":142},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fplan.md",8058,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fplan.md",{"path":144,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":145,"sourceHtmlUrl":146},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fprogress.yml",1188,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fprogress.yml",{"path":148,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":149,"sourceHtmlUrl":150},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fquickstart.md",1831,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fquickstart.md",{"path":152,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":153,"sourceHtmlUrl":154},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fresearch.md",5769,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fresearch.md",{"path":156,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":157,"sourceHtmlUrl":158},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fspec.md",15558,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Fspec.md",{"path":160,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":161,"sourceHtmlUrl":162},"examples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Ftasks.md",13141,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fspecs\u002F001-static-landing-page\u002Ftasks.md",{"path":164,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":165,"sourceHtmlUrl":166},"examples\u002Fstatic-landing-page\u002Fweb\u002Findex.html",12772,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fexamples\u002Fstatic-landing-page\u002Fweb\u002Findex.html",{"path":168,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":169,"sourceHtmlUrl":170},"extension.yml",3805,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fextension.yml",{"path":172,"resourceType":172,"resourceTypeDesc":173,"sizeBytes":174,"sourceHtmlUrl":16},"LICENSE","许可证",1079,{"path":176,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":177,"sourceHtmlUrl":178},"README_zh.md",5985,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002FREADME_zh.md",{"path":180,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":181,"sourceHtmlUrl":182},"README.md",15121,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002FREADME.md",{"path":184,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":185,"sourceHtmlUrl":186},"references\u002Fsuperpowers-bridge.md",8740,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Freferences\u002Fsuperpowers-bridge.md",{"path":188,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":189,"sourceHtmlUrl":190},"references\u002Fworkflow-guide.md",18756,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Freferences\u002Fworkflow-guide.md",{"path":192,"resourceType":193,"resourceTypeDesc":194,"sizeBytes":195,"sourceHtmlUrl":196},"scripts\u002Fe2e-agent-claude.sh","SCRIPT","脚本",19458,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fscripts\u002Fe2e-agent-claude.sh",{"path":198,"resourceType":193,"resourceTypeDesc":194,"sizeBytes":199,"sourceHtmlUrl":200},"scripts\u002Fe2e-smoke.sh",8757,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fscripts\u002Fe2e-smoke.sh",{"path":202,"resourceType":193,"resourceTypeDesc":194,"sizeBytes":203,"sourceHtmlUrl":204},"scripts\u002Fvalidate-extension-metadata.py",5888,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fscripts\u002Fvalidate-extension-metadata.py",{"path":206,"resourceType":193,"resourceTypeDesc":194,"sizeBytes":207,"sourceHtmlUrl":208},"scripts\u002Fvalidate-release-archive.py",7053,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Fscripts\u002Fvalidate-release-archive.py",{"path":210,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":211,"sourceHtmlUrl":212},"templates\u002Fchecklist-template.md",3543,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Ftemplates\u002Fchecklist-template.md",{"path":214,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":215,"sourceHtmlUrl":216},"templates\u002Fconstitution-template.md",4140,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Ftemplates\u002Fconstitution-template.md",{"path":218,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":219,"sourceHtmlUrl":220},"templates\u002Fplan-template.md",4186,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Ftemplates\u002Fplan-template.md",{"path":222,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":223,"sourceHtmlUrl":224},"templates\u002Fspec-template.md",5436,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Ftemplates\u002Fspec-template.md",{"path":226,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":227,"sourceHtmlUrl":228},"templates\u002Ftasks-template.md",7255,"https:\u002F\u002Fgithub.com\u002Fmilos85vasic\u002Fvasic\u002Fblob\u002Fmain\u002F.specify\u002Fextensions\u002Fsuperspec\u002Ftemplates\u002Ftasks-template.md",[]]