coding-workflow

Orchestrate a Plan-Execute-Verify workflow with task.json and progress.txt tracking.

3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/zhaohuanke123/vanko-skill --skill coding-workflow-zhaohuanke123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-workflow
Source: https://github.com/zhaohuanke123/vanko-skill/tree/main/skills/coding-workflow
Command: npx skills add https://github.com/zhaohuanke123/vanko-skill --skill coding-workflow-zhaohuanke123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires subprocess, argparse, re, pathlib, sys, json, git, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you build and evolve software without skipping key steps by orchestrating a disciplined Plan-Execute-Verify (PEV) workflow that separates planning, implementation, and verification.

Core Features & Use Cases

  • Plan-Execute-Verify orchestration: Uses independent Planner, Executor, and Verifier roles to reduce optimistic bias and improve correctness.
  • Documentation Gate: Prevents source code edits unless the required behavior/design documents are present and updated (with a controlled bypass for pure bug fixes).
  • Task-driven, durable development loop: Uses task.json and progress.txt to select the next runnable task, track status, and record testing evidence.
  • Worktree isolation + file ownership: Executes each task in an isolated worktree with explicit file ownership to avoid collisions between subagents.
  • Full verification via tests and consistency checks: Verifier writes/updates tests, runs the full test suite, and checks docs/code/tests consistency before merge.

Quick Start

Run /coding-workflow in a project directory that has been initialized with CLAUDE.md, architecture.md, task.json, and progress.txt, then let the agent execute the next available task through the PEV loop.

Frequently Asked Questions about coding-workflow

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

FAQPage Schema
How do I orchestrate a plan-execute-verify coding workflow with automatic testing and documentation checks?

You can enforce a documentation-first coding workflow by requiring design documents to be present and updated before source code edits are allowed, with a controlled bypass available for pure bug fixes.

How do I prevent git worktree collisions when running multiple agent coding tasks?

To prevent git worktree collisions during agent coding tasks, you execute each task in an isolated worktree with explicit file ownership control, ensuring subagents do not overwrite each other's changes.

Does the plan-execute-verify workflow support automated commits and persistent progress tracking?

Yes, the plan-execute-verify workflow supports automated commits by merging code only after the full test suite passes, while tracking persistent progress via task.json and progress.txt files.

Can I use the coding workflow for fullstack projects with complex task dependencies?

You can use this coding workflow for fullstack projects where tasks have dependencies, because it selects the next runnable task from task.json and manages execution order to satisfy dependency constraints.

What files do I need to initialize before starting automated task orchestration in my repository?

To start automated task orchestration, you need to initialize your project directory with CLAUDE.md, architecture.md, task.json, and progress.txt before running the workflow agent.