{
  "schemaVersion": "1.0",
  "item": {
    "slug": "spec-kit",
    "name": "Spec Kit",
    "source": "tencent",
    "type": "skill",
    "category": "效率提升",
    "sourceUrl": "https://clawhub.ai/AungMyoKyaw/spec-kit",
    "canonicalUrl": "https://clawhub.ai/AungMyoKyaw/spec-kit",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/spec-kit",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=spec-kit",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/spec-kit"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/spec-kit",
    "agentPageUrl": "https://openagent3.xyz/skills/spec-kit/agent",
    "manifestUrl": "https://openagent3.xyz/skills/spec-kit/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/spec-kit/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Spec Kit — Spec-Driven Development",
        "body": "Build high-quality software faster using Spec-Driven Development (SDD). Specifications become executable artifacts that generate working implementations, not just documentation.\n\nHomepage: https://github.github.com/spec-kit/\nGitHub: https://github.com/github/spec-kit"
      },
      {
        "title": "What is Spec-Driven Development?",
        "body": "SDD flips traditional software development:\n\nTraditionalSpec-DrivenSpecs are scaffolding → discardedSpecs are executable → generate codeCode is kingIntent is kingOne-shot promptsMulti-step refinementFocus on \"how\"Focus on \"what\" and \"why\"\n\nCore Philosophy:\n\nIntent-driven development\nRich specifications with guardrails\nHeavy reliance on AI model capabilities\nTechnology-independent process"
      },
      {
        "title": "Prerequisites",
        "body": "OS: Linux, macOS, Windows (PowerShell supported)\nAI Agent: Claude Code, GitHub Copilot, Gemini CLI, or Codebuddy CLI\nPackage Manager: uv\nPython: 3.11+\nGit: Any recent version"
      },
      {
        "title": "Initialize a New Project",
        "body": "# Create new project directory\nuvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>\n\n# Initialize in current directory\nuvx --from git+https://github.com/github/spec-kit.git specify init .\nuvx --from git+https://github.com/github/spec-kit.git specify init --here"
      },
      {
        "title": "Specify AI Agent",
        "body": "# Proactively set AI agent during init\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai claude\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai gemini\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai copilot\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai codebuddy"
      },
      {
        "title": "Script Type (Shell vs PowerShell)",
        "body": "Auto-selected by OS, or force explicitly:\n\n# Force PowerShell (Windows)\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --script ps\n\n# Force POSIX shell (Linux/macOS)\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --script sh"
      },
      {
        "title": "Skip Tool Checks",
        "body": "uvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai claude --ignore-agent-tools"
      },
      {
        "title": "Step 1: Initialize",
        "body": "Run specify init to create project structure with templates.\n\nuvx --from git+https://github.com/github/spec-kit.git specify init my-app --ai claude\n\nCreates:\n\n.speckit/ directory with configuration\nAgent-specific templates\nGit repository structure"
      },
      {
        "title": "Step 2: Define Constitution",
        "body": "Establish core rules and principles for your project.\n\nSlash Command:\n\n/speckit.constitution This project follows a \"Library-First\" approach. \nAll features must be implemented as standalone libraries first. \nWe use TDD strictly. We prefer functional programming patterns.\n\nPurpose: Sets guardrails and organizational principles that all specs must follow."
      },
      {
        "title": "Step 3: Create Specification",
        "body": "Describe what you want to build, not how.\n\nSlash Command:\n\n/speckit.specify Build an application that can help me organize my photos \nin separate photo albums. Albums are grouped by date and can be re-organized \nby dragging and dropping on the main page. Albums are never in other nested \nalbums. Within each album, photos are previewed in a tile-like interface.\n\nBest Practices:\n\nFocus on user scenarios and behaviors\nAvoid tech stack details (AI picks appropriate tech)\nDescribe UI/UX in plain language\nInclude constraints and business rules"
      },
      {
        "title": "Step 4: Refine (Clarify)",
        "body": "Identify and resolve ambiguities in your specification.\n\nSlash Command:\n\n/speckit.clarify Focus on security implications and edge cases\n\nWhat it does:\n\nDetects vague or ambiguous requirements\nAsks clarifying questions\nSuggests concrete implementations\nUpdates spec with resolved details"
      },
      {
        "title": "Step 5: Plan",
        "body": "Generate detailed implementation plan from specification.\n\nSlash Command:\n\n/speckit.plan\n\nOutput:\n\nArchitecture decisions\nFile structure\nImplementation steps\nTesting strategy\nDependencies to install"
      },
      {
        "title": "Step 6: Build",
        "body": "Execute the implementation plan.\n\nSlash Command:\n\n/speckit.build\n\nFeatures:\n\nGenerates code based on spec + plan\nCreates files incrementally\nRuns tests as specified\nCommits progress to Git"
      },
      {
        "title": "Context Awareness: Git Branch-Based",
        "body": "Spec Kit automatically detects the active feature based on your current Git branch.\n\nNaming Convention:\n\n001-feature-name\n002-user-authentication\n003-photo-album-grid\n\nTo switch between specifications:\n\ngit checkout 001-feature-name    # Work on feature 1\ngit checkout 002-user-auth       # Work on feature 2\n\nContext is automatically loaded when you run Spec Kit commands."
      },
      {
        "title": "Phase 1: 0-to-1 (Greenfield)",
        "body": "Focus: Generate from scratch\n\nStart with high-level requirements\nGenerate specifications\nPlan implementation steps\nBuild production-ready applications"
      },
      {
        "title": "Phase 2: Creative Exploration",
        "body": "Focus: Parallel implementations\n\nExplore diverse solutions\nSupport multiple technology stacks\nExperiment with UX patterns\nCompare approaches"
      },
      {
        "title": "Phase 3: Iterative Enhancement (Brownfield)",
        "body": "Focus: Modernization\n\nAdd features iteratively\nModernize legacy systems\nAdapt existing processes\nRefactor with specs"
      },
      {
        "title": "All Slash Commands Reference",
        "body": "CommandPurposeWhen to Use/speckit.constitutionDefine project principlesAt project start/speckit.specifyCreate specificationFor each new feature/speckit.clarifyResolve ambiguitiesWhen spec is vague/speckit.planGenerate implementation planBefore coding/speckit.buildExecute implementationAfter planning"
      },
      {
        "title": "Organizational Constraints",
        "body": "Cloud Providers: Target specific platforms (AWS, Azure, GCP)\nTech Stacks: Enforce approved technologies\nDesign Systems: Integrate enterprise UI libraries\nCompliance: Meet security/regulatory requirements"
      },
      {
        "title": "Technology Independence",
        "body": "Spec Kit works with:\n\nAny programming language\nAny framework\nAny architecture pattern\nAny deployment target"
      },
      {
        "title": "Clone and Setup",
        "body": "git clone https://github.com/github/spec-kit.git\ncd spec-kit"
      },
      {
        "title": "Run CLI Directly",
        "body": "# Fastest feedback - no install needed\npython -m src.specify_cli --help\npython -m src.specify_cli init demo-project --ai claude --script sh"
      },
      {
        "title": "Editable Install",
        "body": "uv venv\nsource .venv/bin/activate  # Windows: .venv\\Scripts\\Activate.ps1\nuv pip install -e .\nspecify --help"
      },
      {
        "title": "Test From Branch",
        "body": "# Push branch first\ngit push origin your-feature-branch\n\n# Test via uvx\nuvx --from git+https://github.com/github/spec-kit.git@your-feature-branch \\\n  specify init demo-branch-test --script ps"
      },
      {
        "title": "Specification Writing",
        "body": "✅ DO:\n\nDescribe user scenarios\nInclude business rules\nMention constraints\nUse plain language\nFocus on behavior, not implementation\n\n❌ DON'T:\n\nSpecify tech stack (let AI choose)\nWrite implementation details\nUse jargon without context\nMake assumptions unstated"
      },
      {
        "title": "Example Good Spec",
        "body": "/speckit.specify Build a task management app where:\n- Users can create projects with color-coded labels\n- Tasks have priorities (High/Medium/Low) with visual indicators\n- Drag-and-drop to reorder tasks within a project\n- Tasks can be assigned to multiple users\n- Due dates trigger notifications 24h before\n- Completed tasks archive automatically after 7 days\n- Mobile-responsive with touch-friendly interactions"
      },
      {
        "title": "Example Bad Spec",
        "body": "/speckit.specify Build a React app with Redux for state management.\nUse Material-UI for components. Store data in PostgreSQL."
      },
      {
        "title": "Command Not Found",
        "body": "Problem: AI agent doesn't recognize /speckit.* commands\nSolution: Re-run specify init in the project directory"
      },
      {
        "title": "Wrong Context Loaded",
        "body": "Problem: Working on wrong specification\nSolution: Check current branch with git branch and switch: git checkout <branch>"
      },
      {
        "title": "Script Type Issues",
        "body": "Problem: PowerShell scripts on macOS or vice versa\nSolution: Force script type: --script sh or --script ps"
      },
      {
        "title": "Agent Tool Missing",
        "body": "Problem: Spec Kit complains about missing AI agent tools\nSolution: Use --ignore-agent-tools flag during init"
      },
      {
        "title": "New Feature Workflow",
        "body": "# 1. Create feature branch\ngit checkout -b 004-dark-mode\n\n# 2. In AI agent chat:\n/speckit.specify Add dark mode toggle to the application. \nSystem should detect OS preference but allow manual override. \nStore preference in localStorage.\n\n# 3. Clarify ambiguities:\n/speckit.clarify Focus on accessibility (WCAG contrast)\n\n# 4. Generate plan:\n/speckit.plan\n\n# 5. Build:\n/speckit.build\n\n# 6. Commit and PR\ngit add .\ngit commit -m \"feat: add dark mode toggle\""
      },
      {
        "title": "Brownfield Enhancement",
        "body": "# 1. Switch to existing feature\ngit checkout 002-user-auth\n\n# 2. Enhance spec:\n/speckit.specify Add OAuth2 login with Google and GitHub providers\n\n# 3. Plan the enhancement:\n/speckit.plan\n\n# 4. Build iteratively:\n/speckit.build"
      },
      {
        "title": "Resources",
        "body": "Documentation: https://github.github.com/spec-kit/\nGitHub Repo: https://github.com/github/spec-kit\nContributing: https://github.com/github/spec-kit/blob/main/CONTRIBUTING.md\nSupport: https://github.com/github/spec-kit/blob/main/SUPPORT.md"
      },
      {
        "title": "Key Principles Summary",
        "body": "Intent over Implementation — Describe what, not how\nSpecifications are Assets — Treat them as primary deliverables\nMulti-step Refinement — Iterate: Constitute → Specify → Clarify → Plan → Build\nContext-Aware — Git branches maintain feature context\nTechnology Agnostic — Process works with any stack\n\nLast updated: 2026-02-28"
      }
    ],
    "body": "Spec Kit — Spec-Driven Development\n\nBuild high-quality software faster using Spec-Driven Development (SDD). Specifications become executable artifacts that generate working implementations, not just documentation.\n\nHomepage: https://github.github.com/spec-kit/\nGitHub: https://github.com/github/spec-kit\n\nWhat is Spec-Driven Development?\n\nSDD flips traditional software development:\n\nTraditional\tSpec-Driven\nSpecs are scaffolding → discarded\tSpecs are executable → generate code\nCode is king\tIntent is king\nOne-shot prompts\tMulti-step refinement\nFocus on \"how\"\tFocus on \"what\" and \"why\"\n\nCore Philosophy:\n\nIntent-driven development\nRich specifications with guardrails\nHeavy reliance on AI model capabilities\nTechnology-independent process\nPrerequisites\nOS: Linux, macOS, Windows (PowerShell supported)\nAI Agent: Claude Code, GitHub Copilot, Gemini CLI, or Codebuddy CLI\nPackage Manager: uv\nPython: 3.11+\nGit: Any recent version\nInstallation & Setup\nInitialize a New Project\n# Create new project directory\nuvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME>\n\n# Initialize in current directory\nuvx --from git+https://github.com/github/spec-kit.git specify init .\nuvx --from git+https://github.com/github/spec-kit.git specify init --here\n\nSpecify AI Agent\n# Proactively set AI agent during init\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai claude\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai gemini\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai copilot\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai codebuddy\n\nScript Type (Shell vs PowerShell)\n\nAuto-selected by OS, or force explicitly:\n\n# Force PowerShell (Windows)\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --script ps\n\n# Force POSIX shell (Linux/macOS)\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --script sh\n\nSkip Tool Checks\nuvx --from git+https://github.com/github/spec-kit.git specify init <project> --ai claude --ignore-agent-tools\n\nThe 6-Step Spec-Driven Process\nStep 1: Initialize\n\nRun specify init to create project structure with templates.\n\nuvx --from git+https://github.com/github/spec-kit.git specify init my-app --ai claude\n\n\nCreates:\n\n.speckit/ directory with configuration\nAgent-specific templates\nGit repository structure\nStep 2: Define Constitution\n\nEstablish core rules and principles for your project.\n\nSlash Command:\n\n/speckit.constitution This project follows a \"Library-First\" approach. \nAll features must be implemented as standalone libraries first. \nWe use TDD strictly. We prefer functional programming patterns.\n\n\nPurpose: Sets guardrails and organizational principles that all specs must follow.\n\nStep 3: Create Specification\n\nDescribe what you want to build, not how.\n\nSlash Command:\n\n/speckit.specify Build an application that can help me organize my photos \nin separate photo albums. Albums are grouped by date and can be re-organized \nby dragging and dropping on the main page. Albums are never in other nested \nalbums. Within each album, photos are previewed in a tile-like interface.\n\n\nBest Practices:\n\nFocus on user scenarios and behaviors\nAvoid tech stack details (AI picks appropriate tech)\nDescribe UI/UX in plain language\nInclude constraints and business rules\nStep 4: Refine (Clarify)\n\nIdentify and resolve ambiguities in your specification.\n\nSlash Command:\n\n/speckit.clarify Focus on security implications and edge cases\n\n\nWhat it does:\n\nDetects vague or ambiguous requirements\nAsks clarifying questions\nSuggests concrete implementations\nUpdates spec with resolved details\nStep 5: Plan\n\nGenerate detailed implementation plan from specification.\n\nSlash Command:\n\n/speckit.plan\n\n\nOutput:\n\nArchitecture decisions\nFile structure\nImplementation steps\nTesting strategy\nDependencies to install\nStep 6: Build\n\nExecute the implementation plan.\n\nSlash Command:\n\n/speckit.build\n\n\nFeatures:\n\nGenerates code based on spec + plan\nCreates files incrementally\nRuns tests as specified\nCommits progress to Git\nContext Awareness: Git Branch-Based\n\nSpec Kit automatically detects the active feature based on your current Git branch.\n\nNaming Convention:\n\n001-feature-name\n002-user-authentication\n003-photo-album-grid\n\n\nTo switch between specifications:\n\ngit checkout 001-feature-name    # Work on feature 1\ngit checkout 002-user-auth       # Work on feature 2\n\n\nContext is automatically loaded when you run Spec Kit commands.\n\nDevelopment Phases\nPhase 1: 0-to-1 (Greenfield)\n\nFocus: Generate from scratch\n\nStart with high-level requirements\nGenerate specifications\nPlan implementation steps\nBuild production-ready applications\nPhase 2: Creative Exploration\n\nFocus: Parallel implementations\n\nExplore diverse solutions\nSupport multiple technology stacks\nExperiment with UX patterns\nCompare approaches\nPhase 3: Iterative Enhancement (Brownfield)\n\nFocus: Modernization\n\nAdd features iteratively\nModernize legacy systems\nAdapt existing processes\nRefactor with specs\nAll Slash Commands Reference\nCommand\tPurpose\tWhen to Use\n/speckit.constitution\tDefine project principles\tAt project start\n/speckit.specify\tCreate specification\tFor each new feature\n/speckit.clarify\tResolve ambiguities\tWhen spec is vague\n/speckit.plan\tGenerate implementation plan\tBefore coding\n/speckit.build\tExecute implementation\tAfter planning\nEnterprise Features\nOrganizational Constraints\nCloud Providers: Target specific platforms (AWS, Azure, GCP)\nTech Stacks: Enforce approved technologies\nDesign Systems: Integrate enterprise UI libraries\nCompliance: Meet security/regulatory requirements\nTechnology Independence\n\nSpec Kit works with:\n\nAny programming language\nAny framework\nAny architecture pattern\nAny deployment target\nLocal Development (Contributing)\nClone and Setup\ngit clone https://github.com/github/spec-kit.git\ncd spec-kit\n\nRun CLI Directly\n# Fastest feedback - no install needed\npython -m src.specify_cli --help\npython -m src.specify_cli init demo-project --ai claude --script sh\n\nEditable Install\nuv venv\nsource .venv/bin/activate  # Windows: .venv\\Scripts\\Activate.ps1\nuv pip install -e .\nspecify --help\n\nTest From Branch\n# Push branch first\ngit push origin your-feature-branch\n\n# Test via uvx\nuvx --from git+https://github.com/github/spec-kit.git@your-feature-branch \\\n  specify init demo-branch-test --script ps\n\nBest Practices\nSpecification Writing\n\n✅ DO:\n\nDescribe user scenarios\nInclude business rules\nMention constraints\nUse plain language\nFocus on behavior, not implementation\n\n❌ DON'T:\n\nSpecify tech stack (let AI choose)\nWrite implementation details\nUse jargon without context\nMake assumptions unstated\nExample Good Spec\n/speckit.specify Build a task management app where:\n- Users can create projects with color-coded labels\n- Tasks have priorities (High/Medium/Low) with visual indicators\n- Drag-and-drop to reorder tasks within a project\n- Tasks can be assigned to multiple users\n- Due dates trigger notifications 24h before\n- Completed tasks archive automatically after 7 days\n- Mobile-responsive with touch-friendly interactions\n\nExample Bad Spec\n/speckit.specify Build a React app with Redux for state management.\nUse Material-UI for components. Store data in PostgreSQL.\n\nTroubleshooting\nCommand Not Found\n\nProblem: AI agent doesn't recognize /speckit.* commands\nSolution: Re-run specify init in the project directory\n\nWrong Context Loaded\n\nProblem: Working on wrong specification\nSolution: Check current branch with git branch and switch: git checkout <branch>\n\nScript Type Issues\n\nProblem: PowerShell scripts on macOS or vice versa\nSolution: Force script type: --script sh or --script ps\n\nAgent Tool Missing\n\nProblem: Spec Kit complains about missing AI agent tools\nSolution: Use --ignore-agent-tools flag during init\n\nWorkflow Examples\nNew Feature Workflow\n# 1. Create feature branch\ngit checkout -b 004-dark-mode\n\n# 2. In AI agent chat:\n/speckit.specify Add dark mode toggle to the application. \nSystem should detect OS preference but allow manual override. \nStore preference in localStorage.\n\n# 3. Clarify ambiguities:\n/speckit.clarify Focus on accessibility (WCAG contrast)\n\n# 4. Generate plan:\n/speckit.plan\n\n# 5. Build:\n/speckit.build\n\n# 6. Commit and PR\ngit add .\ngit commit -m \"feat: add dark mode toggle\"\n\nBrownfield Enhancement\n# 1. Switch to existing feature\ngit checkout 002-user-auth\n\n# 2. Enhance spec:\n/speckit.specify Add OAuth2 login with Google and GitHub providers\n\n# 3. Plan the enhancement:\n/speckit.plan\n\n# 4. Build iteratively:\n/speckit.build\n\nResources\nDocumentation: https://github.github.com/spec-kit/\nGitHub Repo: https://github.com/github/spec-kit\nContributing: https://github.com/github/spec-kit/blob/main/CONTRIBUTING.md\nSupport: https://github.com/github/spec-kit/blob/main/SUPPORT.md\nKey Principles Summary\nIntent over Implementation — Describe what, not how\nSpecifications are Assets — Treat them as primary deliverables\nMulti-step Refinement — Iterate: Constitute → Specify → Clarify → Plan → Build\nContext-Aware — Git branches maintain feature context\nTechnology Agnostic — Process works with any stack\n\nLast updated: 2026-02-28"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/AungMyoKyaw/spec-kit",
    "publisherUrl": "https://clawhub.ai/AungMyoKyaw/spec-kit",
    "owner": "AungMyoKyaw",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/spec-kit",
    "downloadUrl": "https://openagent3.xyz/downloads/spec-kit",
    "agentUrl": "https://openagent3.xyz/skills/spec-kit/agent",
    "manifestUrl": "https://openagent3.xyz/skills/spec-kit/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/spec-kit/agent.md"
  }
}