Skip to content

aiskillstore/marketplace / skills/abdul-haseeb360/spec-kit-claude-code-workflow

spec-kit-claude-code-workflow

Verified

A conceptual skill for guiding the Spec-Kit + Claude Code development workflow

FileKindSize
SKILL.mdskill md7.4 KB
skill-report.jsonconfig11.1 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-18T09:37:08.337Z",
    "slug": "abdul-haseeb360-spec-kit-claude-code-workflow",
    "source_url": "https://github.com/Abdul-Haseeb360/Hackathon-II-AI-Native-Systems/tree/main/.claude/skills/speckit-claude-workflow",
    "source_ref": "main",
    "model": "claude",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "9c0c309aecfdde5d213aa9e5d8dc912479cb3797ec1dd4e772d06cb5e99698c4",
    "tree_hash": "de103a8d167a41bea9e3c61e5dd359bc1626548a8511c75d0d1a27e2be7d4350",
    "provenance": {
      "model_effective": "claude",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "failed",
          "error": "2026-07-18T09:37:08.470393Z ERROR codex_models_manager::manager: failed to refresh available models: Missing environment variable: `HELM_API_KEY`.\n2026-07-18T09:37:08.491985Z ERROR codex_models_manage…"
        },
        {
          "agent": "claude",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "Spec-Kit Claude Code Workflow",
    "description": "Guide specification-driven development with Spec-Kit and Claude Code across planning, implementation, validation, and refinement.",
    "summary": "A practical framework for using specifications to guide Claude Code development work.",
    "icon": "📦",
    "version": "1.0.0",
    "author": "Claude",
    "license": "MIT",
    "category": "coding",
    "tags": [
      "specification-driven-development",
      "claude-code",
      "spec-kit",
      "workflow",
      "requirements"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": []
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "All four static findings are false positives caused by ordinary workflow language. SKILL.md contains conceptual guidance only and does not direct system or network reconnaissance. No prompt-injection, data-exfiltration, or business-logic abuse intent was found.",
    "remediation": [],
    "risk_factor_evidence": [],
    "static_findings": [
      {
        "id": "blocker:SKILL.md:27:system-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "System reconnaissance",
        "file": "SKILL.md",
        "line_start": 27,
        "line_end": 27,
        "snippet": "- Rapid prototyping where specifications would slow development"
      },
      {
        "id": "blocker:SKILL.md:174:system-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "System reconnaissance",
        "file": "SKILL.md",
        "line_start": 174,
        "line_end": 174,
        "snippet": "- Address cases where specifications need rapid changes"
      },
      {
        "id": "blocker:SKILL.md:65:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "SKILL.md",
        "line_start": 65,
        "line_end": 66,
        "snippet": "- Create feedback mechanisms for prompt effectiveness"
      },
      {
        "id": "blocker:SKILL.md:159:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "SKILL.md",
        "line_start": 159,
        "line_end": 160,
        "snippet": "- Monitor and improve workflow effectiveness"
      }
    ],
    "finding_verdicts": [
      {
        "id": "blocker:SKILL.md:27:system-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.99,
        "reason": "The line excludes rapid prototyping from the proposed documentation workflow. It contains no instruction to inspect a system, collect host data, or execute reconnaissance."
      },
      {
        "id": "blocker:SKILL.md:174:system-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.99,
        "reason": "The line addresses changing software specifications during development. It does not request discovery of system information or any security-sensitive activity."
      },
      {
        "id": "blocker:SKILL.md:65:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.99,
        "reason": "The referenced feedback mechanism concerns prompt quality in a development process. No network targets, connections, scanning, or collection of network data are described."
      },
      {
        "id": "blocker:SKILL.md:159:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.99,
        "reason": "The line asks teams to improve their internal workflow process. It does not direct network monitoring, network enumeration, or external data collection."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 184,
    "audit_model": "claude",
    "audited_at": "2026-07-18T09:37:08.337Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Build with Specification-First Workflows",
    "value_statement": "Teams can lose alignment when requirements, implementation, and review use different sources of truth. This skill provides a repeatable Spec-Kit and Claude Code workflow for planning, building, validating, and refining features.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "Spec-Kit workflow",
      "specification-driven development",
      "software requirements",
      "AI coding workflow",
      "implementation validation",
      "CLAUDE.md"
    ],
    "actual_capabilities": [
      "Defines a specification-first sequence for planning, implementation, review, and refinement.",
      "Guides repository-wide and folder-specific CLAUDE.md documentation practices.",
      "Lists inputs needed to connect requirements, architecture documents, and acceptance criteria.",
      "Describes how to give Claude Code specification context during implementation.",
      "Encourages traceability between specification sections and implemented features.",
      "Provides quality checks for specification clarity, implementation alignment, and workflow consistency."
    ],
    "limitations": [
      "It is conceptual guidance and does not create files, run commands, or validate code automatically.",
      "It assumes the team has or can create usable specifications and acceptance criteria.",
      "It does not replace technical design review, testing, or security review.",
      "It does not prescribe a specific Spec-Kit file format or project management tool."
    ],
    "use_cases": [
      {
        "title": "Start a specification-led feature",
        "description": "Turn feature requirements into a clear implementation and validation workflow before coding begins.",
        "target_user": "Individual developer"
      },
      {
        "title": "Standardize a multi-folder repository",
        "description": "Plan root and folder-specific CLAUDE.md guidance that preserves shared conventions and local rules.",
        "target_user": "Technical lead"
      },
      {
        "title": "Improve team delivery reviews",
        "description": "Use specifications and acceptance criteria to check whether completed work matches agreed requirements.",
        "target_user": "Engineering team"
      }
    ],
    "prompt_templates": [
      {
        "title": "Outline a feature workflow",
        "scenario": "Beginner",
        "prompt": "Create a specification-first workflow for this feature: [feature]. Include requirements, acceptance criteria, implementation steps, and review checks."
      },
      {
        "title": "Prepare Claude Code context",
        "scenario": "Intermediate",
        "prompt": "Review this specification and repository context: [details]. List the concise context Claude Code needs before implementing [feature]."
      },
      {
        "title": "Check implementation alignment",
        "scenario": "Advanced",
        "prompt": "Compare this implementation summary: [summary] with this specification: [specification]. Identify unmet requirements, unclear assumptions, and validation steps."
      },
      {
        "title": "Design repository guidance",
        "scenario": "Advanced",
        "prompt": "Propose root and folder-specific CLAUDE.md responsibilities for this repository structure: [tree]. Preserve global conventions and identify justified local overrides."
      }
    ],
    "output_examples": [
      {
        "input": "Create a workflow for adding account notifications.",
        "output": [
          "Requirements and acceptance criteria for notification preferences.",
          "Implementation tasks linked to each requirement.",
          "Validation checks for delivery, preferences, and error handling."
        ]
      },
      {
        "input": "Review a feature against its specification.",
        "output": [
          "A list of requirements that are implemented or missing.",
          "Questions for ambiguous specification sections.",
          "Recommended tests and documentation updates."
        ]
      }
    ],
    "best_practices": [
      "Write testable acceptance criteria before asking an AI tool to implement a feature.",
      "Provide the relevant specification and repository conventions with each implementation request.",
      "Review implementation results against requirements before updating the specification."
    ],
    "anti_patterns": [
      "Do not treat generated code as proof that a requirement is complete.",
      "Do not use vague specifications that lack success criteria or constraints.",
      "Do not create folder-specific guidance that silently conflicts with repository-wide rules."
    ],
    "faq": [
      {
        "question": "What is this skill for?",
        "answer": "It provides conceptual guidance for a specification-driven workflow using Spec-Kit and Claude Code."
      },
      {
        "question": "Does it generate specifications automatically?",
        "answer": "No. It explains what strong specifications should contain and how to use them in a workflow."
      },
      {
        "question": "Can it work with existing projects?",
        "answer": "Yes. Use it to organize existing requirements, conventions, and validation practices."
      },
      {
        "question": "Does it require a multi-folder repository?",
        "answer": "No. Multi-folder guidance is optional and is useful only when local rules are needed."
      },
      {
        "question": "Does it replace testing?",
        "answer": "No. Teams should still run appropriate tests, reviews, and security checks."
      },
      {
        "question": "Can Codex use this workflow?",
        "answer": "Yes. The workflow concepts apply to Codex, Claude, and Claude Code when the relevant context is supplied."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 184
    }
  ]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall