Skip to content
cccskills
FreePublished on GitHub

formax-rolling-plan-loop-workflow

Use when the user wants a reusable rolling execution pattern (README + TODO-INDEX) like plans/web-reference-react-refactor, and wants to run delivery in small validated loops.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md1.8 KB
  • references/README.template.md733 B
  • references/TODO-INDEX.template.md634 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Formax Rolling Plan Loop Workflow

Goal

快速创建并维护一个“滚动循环执行”计划目录,结构与 plans/web-reference-react-refactor/ 一致:

  • README.md:目标、边界、固定执行循环
  • TODO-INDEX.md:只保留未完成任务

When to use

  • 用户明确要求“模仿 plans/web-reference-react-refactor 的循环方式”。
  • 用户希望以固定循环推进实现:实现 -> 定向测试 -> codex review -> 提交。
  • 用户多次重复同类流程,想固化为可复用模式。

Output contract

在 plans/<topic-slug>/ 下创建(或更新):

  1. README.md
  2. TODO-INDEX.md

可选:

  1. 在 plans/TODO-INDEX.md 增加该计划入口(通常放在“并行参考”)。

Default loop template

每个切片固定流程:

  1. 实现(最小改动)
  2. 定向测试
  3. codex review --uncommitted -c model="gpt-5.4" -c model_reasoning_effort="medium" -c service_tier="fast"
  4. 提交(Conventional Commit)

Required guardrails

  • 不在同一切片混入无关重构。
  • 不做“测试全量覆盖”作为迭代默认命令(除非用户明确要求)。
  • TODO-INDEX.md 只保留未完成项;已完成项不回填,历史以 Git commit 为准。

Regeneration rules

当 TODO-INDEX.md 清空时:

  1. 仅从同目录 README.md 派生下一批。
  2. 按可提交的小切片拆分(建议 2-8 文件)。
  3. 保持固定循环,不跳步。

References

  • 模板:references/README.template.md
  • 模板:references/TODO-INDEX.template.md

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an xhigh subagent is actually needed before writing a todo or code.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when adding or changing any Approval prompt/presenter.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when implementing or extending /config (storage, prompt injection, request params, UI-only toggles) with tests and strict UI parity.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when working on Formax code changes and you need a disciplined dev loop: keep a single mainline task, avoid scope drift, run only targeted tests (no coverage), avoid partial staging (MM), run mandatory review before commit, include an incremental optimization check, and keep commits small and reviewable.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when implementing/debugging Ctrl+O Expanded Transcript (second view) and thinking persistence in the REPL.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay parity with Claude Code).

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

See all skills by yusifeng

Report a problem with this skill