paceaitian

Paceflow — Productivity skill for Claude Code

Productivity community

Deterministic workflow enforcement and persistent engineering memory for long-running coding agents.

How to install Paceflow

This entry records only its repository, not the path inside it, so there is no exact command to give. Open paceaitian/paceflow and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Paceflow does

Deterministic workflow enforcement and persistent engineering memory for long-running coding agents.

Alternatives in Productivity

  • Performance Optimization Skill — Systematic performance analysis and optimization for RTK CLI tool, focusing on startup time (<10ms), memory us 11.9k ★
  • Build In Public — Build-in-Public — generate posts from your engineering work, anonymize, and schedule via Buffer 705 ★
  • DeduplicateMemory — You are an expert memory organizer 250 ★

README

PACEflow

[![CI](https://github.com/paceaitian/paceflow/actions/workflows/ci.yml/badge.svg)](https://github.com/paceaitian/paceflow/actions/workflows/ci.yml) [![GitHub release](https://img.shields.io/github/v/release/paceaitian/paceflow)](https://github.com/paceaitian/paceflow/releases) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

**English** | [简体中文](README.zh-CN.md)

**Deterministic workflow enforcement and persistent engineering memory for long-running coding agents.**

PACEflow keeps coding agents on a verifiable engineering workflow during long, stateful tasks. It enforces workflow transitions at tool boundaries, persists task state outside the model context, and restores that state across sessions and context compaction.

PACEflow ships as a **Claude Code plugin** that also installs into **OpenAI Codex CLI** (same plugin directory, same hook scripts, artifact writes via a bundled MCP server on Codex — see [Codex CLI (MVP)](#codex-cli-mvp)). Its underlying reliability model—deterministic gates, persistent artifacts, verification, and review—addresses problems common to long-running coding agents.

Why PACEflow?

Long-running coding-agent tasks introduce workflow continuity failures:

  • implementation begins before the plan is approved;
  • task state drifts during a long session;
  • important context disappears after compaction or a new session;
  • verification or review is skipped at closure;
  • process instructions written only in prompts remain probabilistic.

PACEflow addresses these failures at the workflow layer. Instead of asking the model to remember every transition, it places deterministic hooks around tool use and session completion, persists the working state, and delegates record-keeping to a dedicated `artifact-writer` agent.

Deterministic gates, not deterministic intelligence

The model still plans, implements, verifies, and reviews the code. A PACEflow gate confirms that a required step occurred in the e