Devflow Native

Devflow Native is a repo-local workflow companion for Claude Code, Codex, and other AI coding agents.

Codex, Claude Code, Gemini, Superpowers, and shell sessions do the work. Devflow records the shared project truth they need to start, finish, and hand off work without losing context.

What It Is

• A local-first state layer for active work, agent sessions, gate evidence, risks, and handoffs.
• A plugin-first workflow surface for Codex and Claude Code, backed by the same CLI and MCP contracts.
• A repo-local record of what changed, what was verified, what is still risky, and what the next session should do.

What It Is Not

• It is not another autonomous coding agent.
• It is not a dashboard-first app.
• It is not a replacement for Codex, Claude Code, Gemini, Superpowers, Hermes, git, tests, or PR review.
• It is not an HTML artifact generator as source of truth. Generated artifacts are optional views over structured local state.

Why Continuity Matters

AI coding agents make implementation faster, but long-running development still breaks at session boundaries:

• the next session repeats exploration that already happened
• failing or skipped checks get flattened into confident summaries
• active work, changed files, and review state scatter across chat history, terminals, git, and local notes
• a maintainer cannot tell whether a task is actually done or only claimed done

Devflow's job is to keep that workflow state compact, local, inspectable, and usable by the next agent session.

Primary UX

The primary surface is the repo-local plugin at plugins/devflow.

Devflow is meant to be installed by the coding agent you already use. A maintainer should be able to paste one bootstrap prompt into Codex or Claude Code, let that agent clone or inspect Devflow, install the repo-local harness, verify MCP/plugin/hook wiring, and then restart the agent host with Devflow context active.

Copy this into Codex or Claude Code from the repository you want to equip:

Install Devflow Native for this repository.

Use https://github.com/Sungblab/devflow-native as the source. Do not replace
existing project instructions. Inspect the current repo first, install only the
missing Devflow harness pieces, configure MCP/plugin/hook integration when the
host supports it, verify the result, and tell me exactly whether I need to
restart Codex or Claude Code.

Expected verification:
- Devflow CLI help works.
- Source install or npm link exposes a `devflow` command.
- Devflow doctor/status work for this repo.
- Devflow harness health is ok, or the remaining host limitation is explicit.
- Existing AGENTS.md, CLAUDE.md, README, tests, and project rules are preserved.

When enabled in Codex or Claude Code, the plugin is expected to:

• load compact doctor and status context at session start
• detect fast maintainer prompts such as ㄱㄱ, 이어가, 끝내, or pr ㄱㄱ
• preserve local execution rules, active work, gate evidence, and latest handoff state
• use Superpowers as an optional workflow profile when available, not as a core dependency
• avoid generating HTML unless the maintainer asks for a visual artifact or the state is too dense for text

The CLI and MCP server are the local engine behind that plugin. They remain useful for debugging, tests, and hosts that do not support plugin hooks yet.

First Plugin Loop

Codex or Claude Code opens the repo
  -> Devflow SessionStart hook injects compact repo context

Maintainer says "ㄱㄱ" or "이어가"
  -> Devflow UserPromptSubmit hook classifies the workflow intent
  -> the agent uses status, active work, and handoff state before editing

Maintainer says "끝내" or "pr ㄱㄱ"
  -> Devflow finish skill checks docs impact, gates, risks, and next prompt
  -> completion evidence is recorded in .devflow/state/events.jsonl

Local Engine

The local engine exposes direct commands for the installing agent, development, and fallback use:

npm link
devflow --help
devflow --version
node packages/cli/src/index.js --help
node packages/cli/src/index.js doctor --platform windows-powershell --json
node packages/cli/src/index.js status --simple
node packages/cli/src/index.js finish --json
node packages/cli/src/index.js prompt next
node packages/cli/src/index.js prompt latest
npm run mcp:stdio

Before npm publication, npm link is the intended local install path for an agent-led setup. The package name is @sungblab/devflow-native, and npm run pack:check verifies that the packed tarball installs into a temporary consumer project and exposes the devflow binary. Run npm run publish:check before any real npm release. It performs the package install check plus npm publish --dry-run and package contents guards.

devflow finish records local evidence in .devflow/state/events.jsonl. It also writes the latest human-readable prompt projection to .devflow/next-prompt.md. devflow prompt next emits an ad hoc compact handoff prompt, and devflow prompt latest reads the persisted prompt for the next session.

Core Loop

Most AI coding tools optimize for code generation or agent orchestration. Devflow optimizes for continuity:

• What is this project supposed to be?
• What task is active now?
• Which agent sessions touched it?
• Which files changed?
• Which checks passed or failed?
• Which reviews are unresolved?
• What should the next session do?

The durable source of truth is structured .devflow state and append-only events. CLI, MCP, and plugin skills are different ways to read or write that same state.

Research Boundary

Research notes, paper drafts, pilot fixtures, and non-public evaluation data are kept in a separate private repository. This public repository contains the product implementation and public product documentation only.

First-Class Concepts

• Project contract: durable repo rules, architecture boundaries, docs index, test strategy, and quality gates.
• Work item: a feature, fix, audit, cleanup, or release slice.
• Session: a Codex, Claude, Gemini, or manual terminal session attached to a work item.
• Gate: a command or external review that proves a slice is ready.
• Handoff: a generated next-session prompt plus evidence from the last run.
• Artifact: an optional generated HTML or text view for dense reviews, split plans, timelines, or handoffs. Artifacts are views, not source of truth.

Documentation

• Quickstart
• Release Checklist
• Product Plan
• Architecture
• Research Boundary
• Roadmap

Repository Structure

packages/core     shared product model, local state, gates, handoff contracts
packages/cli      terminal command surface over core contracts
packages/mcp      MCP handler and stdio transport over the same contracts
packages/adapters agent/session history adapters
plugins/devflow   repo-local Codex and Claude Code plugin drafts
docs              product, architecture, roadmap, examples, and public notes
templates         future project scaffold templates

Current MVP

The current MVP is plugin-first and MCP-backed:

• plugins/devflow/.codex-plugin/plugin.json
• plugins/devflow/.claude-plugin/plugin.json
• plugins/devflow/hooks/hooks.json
• plugins/devflow/skills/start/SKILL.md
• plugins/devflow/skills/finish/SKILL.md
• packages/mcp/src/stdio.js
• packages/cli/src/index.js

The MCP package exposes the same core contracts through devflow.doctor, devflow.status, devflow.finish, devflow.record_gate, devflow.gates_run, devflow.next_prompt, and devflow.handoff_latest, plus work, split, prompt, session, and health tools.

devflow finish --json now returns a false-completion guard contract with canClaimDone, doneBlockers, changed files, gate evidence, skipped or failed gates, remaining risks, a structured handoff, and the next-session prompt.

Status

This repository is still an MVP. The local CLI, MCP handler layer, and repo-local plugin drafts are present. Richer artifact generation, hosted sync, and broader adapter coverage are later work.