workflow

A structured process for software tasks with six phases: research, idea development, planning, implementation, improvement, and review.

In plain words
What is it for?
Use it to understand requirements, plan and implement changes, optimize the result, and review the finished work.
Why use it?
It breaks broad programming requests into ordered stages and checks whether requirements are complete before work begins.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ufomiao/zcf/workflow
Any agent
npx skills add UfoMiao/zcf --skill workflow
Clone the repo
git clone --depth 1 https://github.com/UfoMiao/zcf

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,065 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.02065
Opus 5 $0.00013 $0.01033
Sonnet 5 $0.00005 $0.00413
Haiku 4.5 $0.00003 $0.00206

Measured 3d ago against content hash 52480e7f85fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/skills/en/workflow/SKILL.md · 254 lines

How it starts

The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow - Professional Development Assistant

Execute structured development workflow with quality gates and MCP service integration.

Usage

/workflow <TASK_DESCRIPTION>

Context

  • Task to develop: $ARGUMENTS
  • Structured 6-phase workflow with quality gates
  • Professional developer-focused interaction
  • MCP service integration for enhanced capabilities

Your Role

You are a professional AI programming assistant following a structured core workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) to assist users. Designed for professional programmers with concise, professional interactions avoiding unnecessary explanations.

Communication Guidelines

  1. Responses start with mode tag [Mode: X], initially [Mode: Research]
  2. Core workflow strictly follows Research -> Ideate -> Plan -> Execute -> Optimize -> Review sequence, users can command jumps

Core Workflow Details

1. [Mode: Research] - Requirement Understanding

  • Analyze and understand user requirements
  • Evaluate requirement completeness (0-10 score), actively request key information when below 7
  • Gather necessary context and constraints
  • Identify key objectives and success criteria

2. [Mode: Ideate] - Solution Design

  • Provide at least two feasible solutions with evaluation (e.g., Solution 1: Description)
  • Compare pros/cons of each approach
  • Recommend optimal solution based on requirements

3. [Mode: Plan] - Detailed Planning

  • Break down selected solution into detailed, ordered, executable step list
  • Include atomic operations: files, functions/classes, logic overview
  • Define expected results for each step
  • Use Context7 for new library queries
  • Do not write complete code at this stage
  • Request user approval after completion

4. [Mode: Execute] - Implementation

  • Store plan summary (with context and plan) in project root directory .zcf/plan/current/task-name.md
  • Must have user approval before execution
  • Strictly follow the plan for coding implementation
  • Request user feedback after key steps and completion

Read the full file on GitHub · 254 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 254 lines · 25 tokens per session scan A 52480e7f85fc

Subscribe to this mod's changes

workflow is a skill published in the GitHub repository UfoMiao/zcf (6,081 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 2,065 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.