Haowei
Community@whw23 · Shanghai
Haowei (whw23) maintains 32 Spec Kit skills for spec-driven development: feature specification, planning, task generation, Git branching, and bug remediation.
Agent Skills by Haowei
Showing 32 vetted skills indexed across 1 GitHub repositories.
whw23speckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
whw23speckit-companion-specify
Generates prioritized feature specifications with user stories, requirements, and quality checklists for spec-kit projects.
whw23speckit-companion-tasks
Generates dependency-ordered task lists organized by user story from spec-kit plans.
whw23speckit-git-remote
Detects the Git remote URL and parses GitHub repository owner and name.
whw23speckit-git-validate
Validates Git branch names against spec-kit feature branch naming conventions.
whw23speckit-bug-assess
Assess bug reports against the codebase and write structured remediation assessments.
whw23speckit-git-initialize
Initializes a Git repository with an initial commit in spec-kit projects.
whw23speckit-companion-mark-complete
Marks the active spec-kit feature as completed in .spec-context.json via a Python script.
whw23speckit-constitution
Creates and updates project constitution files while syncing dependent spec-kit templates.
whw23speckit-implement
Executes spec-kit implementation plans by processing tasks.md phases with checklist validation and progress tracking.
whw23speckit-converge
Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.
whw23speckit-companion-classify
Classifies change size as small, normal, or oversized for spec-kit workflow routing.
whw23speckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.
whw23speckit-clarify
Identifies underspecified areas in feature specs through targeted clarification questions.
whw23speckit-plan
Generates implementation plans, research notes, and design contracts from feature specifications.
whw23speckit-agent-context-update
Updates the managed Spec Kit section in coding agent context files.
whw23speckit-git-feature
Creates numbered git feature branches for spec-kit specification workflows.
whw23speckit-analyze
Analyzes spec.md, plan.md, and tasks.md for inconsistencies, gaps, and constitution violations.
whw23speckit-companion-capture-implement
Records per-task implementation progress into .spec-context.json for the SpecKit Companion GUI.
whw23speckit-companion-capture-plan
Writes plan completion state into .spec-context.json for the SpecKit Companion GUI.
whw23speckit-companion-implement
Executes spec-kit tasks.md phases in dependency order and marks specs complete.
whw23speckit-companion-capture-tasks
Writes tasks completion state into .spec-context.json for the SpecKit Companion GUI.
whw23speckit-bug-test
Validates that a recorded bug fix resolves the reported issue and writes a verification report.
whw23speckit-companion-plan
Generates implementation plans with research and design artifacts for spec-kit projects.
Frequently Asked Questions About Haowei
FAQPage SchemaWhat tasks can I perform with whw23's Spec Kit skills?▼
You can create feature specifications from natural language, run clarification passes, generate implementation plans and dependency-ordered task lists, convert tasks to GitHub issues, manage feature branches and commits, assess and fix bugs, and run the full specify-to-implement pipeline hands-off via companion-auto.
Who are these Spec Kit skills designed for?▼
Software developers and engineering teams practicing spec-driven development inside Spec Kit projects. They suit engineers who want structured spec.md, plan.md, and tasks.md artifacts, plus leads who need cross-artifact consistency analysis and GitHub issue generation from design documents.
What is required to run these skills?▼
Every skill requires an existing Spec Kit project structure containing a .specify/ directory. Git-related commands additionally expect a Git repository, and taskstoissues requires GitHub integration with a detected remote URL. No other external dependencies are declared in the manifest.
How does the Companion pipeline track progress?▼
Companion capture commands write each pipeline step (specify, plan, tasks, implement) into a .spec-context.json file consumed by the Companion GUI. The status command reports the current step, recorded decisions, and next action, while resume continues the pipeline from the last completed step.
How do the bug-handling skills work together?▼
The bug lifecycle runs in three stages: bug-assess evaluates a pasted report or URL against the codebase and proposes remediation, bug-fix applies that remediation and records the changes, and bug-test validates the fix is resolved and stores a verification report.