Chad Woolley
Community@thewoolleyman · San Francisco, CA
Ex-GitLab, Ex-Pivotal, Ex-IBM, Open Source. Coder/hacker/sysadmin/ops for 40+ years. Apple II -> mainframes -> web since the web came out -> agentic AI -> ?
Agent Skills by Chad Woolley
Showing 49 vetted skills indexed across 3 GitHub repositories.
thewoolleymanopenspec-apply-change
Implements tasks from an OpenSpec change using the openspec CLI.
thewoolleymanopenspec-explore
Explores ideas and investigates codebases as a thinking partner before creating OpenSpec change proposals.
thewoolleymanopenspec-verify-change
Verify implementation completeness, correctness, and coherence against OpenSpec change artifacts.
thewoolleymanopenspec-new-change
Scaffolds a new OpenSpec change directory with artifact workflow instructions.
thewoolleymanopenspec-archive-change
Archives completed OpenSpec changes with artifact, task, and spec sync checks.
thewoolleymanopenspec-onboard
Guides users through a complete OpenSpec change workflow cycle with narrated phases.
thewoolleymanopenspec-propose
Generates complete OpenSpec change proposals with design, specs, and task artifacts.
thewoolleymanopenspec-bulk-archive-change
Archive multiple completed OpenSpec changes with conflict detection and spec synchronization.
thewoolleymanopenspec-continue-change
Creates the next OpenSpec change artifact by following the schema-driven workflow status.
thewoolleymanopenspec-sync-specs
Sync delta specs from an OpenSpec change into main specification files.
thewoolleymanopenspec-ff-change
Generates all OpenSpec change artifacts in one pass using the openspec CLI.
thewoolleymanlivespec-seed
Authors the initial livespec specification tree for a new project from a chosen template.
thewoolleymanlivespec-next
Ranks the next spec-side action over proposed changes and history, emitting structured JSON.
thewoolleymanlivespec-propose-change
Files a proposed change against a livespec specification under the proposed_changes directory.
thewoolleymanlivespec-doctor
Runs livespec doctor checks against a spec tree and surfaces findings as JSON or dialogue.
thewoolleymanlivespec-critique
Critique livespec specifications to surface ambiguities, contradictions, and missing rules as actionable findings.
thewoolleymanlivespec-help
Explains livespec capabilities and routes users to the correct livespec operation.
thewoolleymanlivespec-prune-history
Prunes old vNNN snapshots from a livespec specification history directory.
thewoolleymanlivespec-revise
Accepts or rejects pending proposed specification changes and snapshots results as versioned history revisions.
thewoolleymanV3 MCP Optimization
Implement MCP transport optimizations and resource pooling for claude-flow v3 deployments.
thewoolleymanstream-chain
Orchestrate multi-step streaming agent workflows with chained execution and context propagation.
thewoolleymansparc-methodology
Coordinate multi-agent development workflows across specification, architecture, implementation, testing, and deployment.
thewoolleymanHooks Automation
Coordinate Claude Flow hooks across swarm agents for automated development workflows.
thewoolleymanV3 CLI Modernization
Modernize claude-flow v3 CLI with interactive prompts and modular commands.
Frequently Asked Questions About Chad Woolley
FAQPage SchemaWhat tasks can I accomplish with thewoolleyman's skills?▼
You can orchestrate Claude Flow agent swarms, optimize AgentDB vector search with HNSW indexing and quantization, automate GitHub releases and multi-repo synchronization, run verification with automatic rollback, and manage livespec specifications through seed, propose-change, critique, revise, doctor, and prune-history operations.
Who are these skills designed for?▼
They target developers and operators building agentic systems with claude-flow v3, agentic-flow, and AgentDB. Maintainers managing GitHub releases, code review, and project boards across multiple repositories, plus teams practicing specification-driven development with livespec, will find directly applicable skills.
How do the livespec skills work in practice?▼
Run livespec-seed to author an initial spec tree, livespec-propose-change to file amendments under proposed_changes/, livespec-revise to accept or reject proposals and snapshot a vNNN history revision, and livespec-doctor to check structural and LLM-driven invariants. livespec-next ranks the next spec-side action as JSON.
What permissions and invocation controls do these skills use?▼
Livespec skills declare allowed-tools such as bash, read, write, and edit, with read-only operations like doctor and next restricted accordingly. livespec-prune-history sets disable-model-invocation: true, so destructive history pruning requires explicit user invocation via /skill:livespec-prune-history.
What are the prerequisites for using these skills?▼
Skills assume a Claude Flow or claude-flow v3 environment with MCP support; AgentDB skills require an AgentDB deployment for vector storage and ReasoningBank integration. GitHub skills require repository access for Actions, releases, and project boards, while livespec skills operate on a SPECIFICATION/ spec_root directory tree.