weaver-base

Parse a spec, implement requirements, spawn a verifier, and create a PR.

3|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/harivansh-afk/claude-code-vertical --skill weaver-base
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weaver-base
Source: https://github.com/harivansh-afk/claude-code-vertical/tree/main/skills/weaver-base
Command: npx skills add https://github.com/harivansh-afk/claude-code-vertical --skill weaver-base

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end lifecycle of a weaver, enabling automated spec execution, verification, and PR creation to accelerate software delivery.

Core Features & Use Cases

  • Spec-driven weaving: Parses a plan spec and implements required changes.
  • Verifier orchestration: Spawns a verifier subagent to validate outputs.
  • Iteration control: Repeats builds until verification passes (up to five iterations).
  • PR generation: Creates and pushes a PR once verification succeeds.
  • Status journaling: Writes results to .claude/vertical/plans/<plan-id>/run/weavers/w-<nn>.json.

Quick Start

Trigger a weave by providing a plan and spec; the weaver-base will implement the spec, spawn a verifier, iterate until pass, and create a PR.

Frequently Asked Questions about weaver-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate spec verification and pull request generation?

Spec verification and pull request generation are automated by parsing a spec, implementing requirements, and spawning a verifier to validate outputs. The process iterates until verification passes and then creates a pull request.

What happens when spec verification fails during automated orchestration?

When spec verification fails, the orchestration process iterates and re-implements the requirements. It repeats the build and verification cycle up to five iterations until the verification passes.

How do I track automated pull request status updates in JSON?

Automated pull request status updates are tracked in JSON files written to the designated run directory. The weaver outputs results to the .claude/vertical/plans/<plan-id>/run/weavers/w-<nn>.json path.

Do I need a building spec and verification spec to start automated weaving?

A building spec and verification spec are required to start automated weaving. The weaver reads both sections from the plan to implement requirements and spawn the verification subagent.

What's the best way to orchestrate verifiers for spec-driven development?

The best way to orchestrate verifiers for spec-driven development is using an automated lifecycle that parses a spec, implements changes, and spawns a verifier subagent to validate outputs before creating a PR.