skills.rest
yagizdo
yagizdoCOMMUNITY
Explore all skills by this author →
Website𝕏@yagizdoGitHub

work

Execute plan files into feature branches, tested commits, and pull requests.

10|1|Updated Mar 2, 2026
Search Tags:#testing#commit#branching#execution#plan#work#pull-request
One-click install
npx skills add https://github.com/yagizdo/quiver --skill work-yagizdo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/yagizdo/quiver/tree/main/skills/work
Command: npx skills add https://github.com/yagizdo/quiver --skill work-yagizdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute plans and specifications in a structured, repeatable way to turn ideas into shipped features with proper versioning and traceability.

Core Features & Use Cases

  • Read a plan file (e.g., .claude/plans/ or a provided spec) to clarify requirements and scope.
  • Create and switch to a descriptive feature branch, implement tasks with continuous testing, and commit incrementally.
  • Ship changes by opening a PR and aligning the work with the plan, tests, and quality gates.

Quick Start

Provide a plan or task list and let the work skill execute it by creating a feature branch, implementing tasks with tests, and shipping a PR.

Frequently Asked Questions about work

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

FAQPage Schema
How do I execute a development plan and automatically ship a pull request?▼

To execute a development plan, you provide a specification file or task list. The workflow guides branch setup, incremental task execution with continuous testing, and opens a pull request once quality checks pass.

What is the process for turning a specification file into shipped features?▼

Turning a specification into shipped features requires a multi-phase workflow: loading and clarifying the plan, setting up a feature branch, building tasks with tests, running quality checks, and shipping a pull request.

Do I need a plan file to use this structured execution workflow?▼

Yes, you need a plan file located in the .claude/plans/ directory or a user-provided spec and task list available to guide the execution phases and track progress.

Can I commit changes directly to the default branch while executing a plan?▼

No, committing to the default branch is prevented without explicit permission. The workflow enforces creating and switching to a descriptive feature branch before implementing tasks.

How are tasks tracked during plan execution and incremental commits?▼

Tasks are tracked using TodoWrite throughout the build phase. This ensures incremental commits align with the plan, tests are run continuously, and progress is monitored against the specification.

What happens if tests fail during the feature branch implementation phase?▼

The workflow requires continuous testing during the build phase. If tests fail, tasks are marked incomplete, preventing incremental commits and the final pull request until quality gates pass.

Related Skills

Explore More Software Engineering Skills→
AsiaOstrichAsiaOstrich
6

plan

Generate plan.json files from specifications, OpenSpec changes, or free-text requirements.

Community
Advanced
thesyntaxninjathesyntaxninja
2

finishing-a-development-branch

Verify feature branch readiness and present merge, pull request, or keep options.

Community
Intermediate
AnveioAnveio
1

claude-agent-sdk

Build autonomous coding agents with the Claude Agent SDK for TypeScript.

Community
Advanced
telagodtelagod
68

git-workflow

Implement and manage Git workflows with branching, commit, and pull request guidelines.

Community
Intermediate