slice

Process repository handoff tasks into specs, implementations, and archived outcomes.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/yearofthedan/weaver --skill slice-yearofthedan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slice
Source: https://github.com/yearofthedan/weaver/tree/main/.claude/skills/slice
Command: npx skills add https://github.com/yearofthedan/weaver --skill slice-yearofthedan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the handoff-to-implementation workflow so agents and developers do not have to manually manage specs, cross-file refactors, test cycles, and archival steps. It ensures work is processed in queue order, architectural forks are resolved before mechanical edits, and each change is verified and committed with tests.

Core Features & Use Cases

  • Spec-first workflow: Create missing specs from templates, capture open decisions, and commit the spec before any implementation begins.
  • Neighborhood batching and execution: Group acceptance criteria that touch the same files, dispatch execution-agent batches to write failing tests, implement changes, run pnpm check, and commit per-AC.
  • Verification and archival: Require pnpm check passing, update handoff.md by removing completed entries, archive the spec with an Outcome and reflection, and record any cross-cutting gotchas.
  • Human-in-the-loop safety: Resolve architectural choices with the user when needed and require explicit approval before proceeding to the next queued slice.

Quick Start

Read docs/handoff.md, confirm or create the spec for the first task, resolve any open design decisions, dispatch execution-agent batches to implement grouped ACs with tests and pnpm check, commit and archive the spec, then request user approval to continue.

Frequently Asked Questions about slice

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

FAQPage Schema
How do I automate task handoff to code implementation with specs and tests?

Task handoff automation picks up queued tasks from docs/handoff.md, generates missing specs, dispatches execution agents to write tests, implements changes, and commits results per acceptance criteria.

What is a spec-first workflow for task orchestration?

A spec-first workflow creates a specification document from a template, captures open design decisions, and commits the spec before any code implementation or mechanical edits begin.

How do I group acceptance criteria for batch code refactoring?

Grouping acceptance criteria by neighborhood batches together criteria that touch the same files, allowing execution agents to write failing tests, implement changes, and run pnpm check efficiently.

Does this task orchestration workflow require pnpm check to pass before committing?

Yes, pnpm check must pass before committing any changes. The workflow requires verification to succeed before updating the handoff queue and archiving the spec with outcomes.

Can I use this automated implementation workflow without a docs/handoff.md file?

No, this workflow operates specifically on projects using docs/handoff.md and docs/specs directories to manage the task queue, specifications, and archival outcomes.

When should I require human approval during automated task implementation?

Human approval is required to resolve architectural choices and design decisions before mechanical edits, and explicit approval is needed before proceeding to the next queued slice.