Coding

Process Keeper

Try it

Backfill development history and keep compact process logs

What it does

Backfill project timelines, capture key decisions and fixes, and extract reusable process notes from development work.

The skill document

Process Keeper

Use this skill when you want to turn project activity into a lightweight, reusable process log.

Best for

  • backfilling what happened so far in a project
  • recording important decisions, fixes, and turning points
  • keeping a compact history for future review
  • extracting article-ready notes from development work
  • maintaining a simple process trail without flooding the repo

Good triggers

  • "Backfill the history so far"
  • "Record this decision"
  • "Turn this work into a retrospective"
  • "Keep a process log for this project"
  • "Extract reusable notes from this iteration"

What it does

This skill helps you:

  • reconstruct a project timeline from commits, files, and conversation context
  • capture only meaningful nodes: problem, decision, change, result, lesson
  • keep the process notes compact and readable
  • turn process notes into reusable summaries, outlines, or narrative material

What it is not

  • not a task manager
  • not a daily journal
  • not a code review tool
  • not a replacement for feature specs
  • not a place to dump every tiny edit

Core workflow

  1. Find the project root.

    • Prefer the active repository.
    • If the repo has no process notes yet, create docs/process/.

  2. Backfill first, then continue.

    • Reconstruct the timeline from commits, files, and available context.
    • Capture only the meaningful nodes.
    • Avoid transcript-style narration.

  3. Keep three layers.

    • HISTORY.md for the timeline
    • PROCESS_GUIDE.md for recording rules
    • TEMPLATE.md for reusable entry structure

  4. Record at key nodes.

    • major UI or UX changes
    • architecture or versioning changes
    • bug fixes with a clear cause
    • design disagreements that get resolved
    • successful or failed verification

  5. Extract reusable material when asked.

    • retrospective
    • project narrative
    • article outline
    • "how we solved it" notes

Output style

Prefer compact records over long narrative blocks.

Default fields

  • time
  • context
  • problem
  • decision
  • change
  • result
  • lesson
  • article angle

Short version

Use a short version when the user only needs a quick record.

  • what happened
  • why it changed
  • what changed after
  • how to move faster next time

Public-use notes

  • Keep public output free of private project names, private paths, and internal-only notes.
  • Keep examples generic so they work in any repository.
  • If a tiny edit did not change the direction, skip it.

Compatible use

This skill is designed to work with local coding agents and project assistants that can read files and write process notes.

Examples:

  • Codex-style local agents
  • Claude-style local agents
  • editor-integrated agents
  • other repo-aware coding assistants

Files

  • PROCESS_GUIDE.md
  • references/process-template.md
  • references/examples.md
  • agents/openai.yaml

Related skills

process-keeper

工作流记录与复用：记录开发过程中的关键决策、问题修复、转折点，沉淀为可复用的流程日志。Invoke when user asks 记录流程、任务复盘、过程记录、日志记录、决策记录.

1 installs

backlog-planner

Turn a feature idea, conversation context, or rough notes into researched, detailed, dependency-ordered checkbox tasks appended to the project's roadmap/backlog file — exactly the format goal-runner consumes, so a fresh unattended session can execute them. Grounds every task in the actual codebase before writing it (grep/read or Explore scouts; think-like-fable rigor if installed), puts what + done-when on the checkbox line with verified files, acceptance criteria, and a verification command in plain sub-bullets, and labels assumptions. Appends to the existing ROADMAP.md/BACKLOG.md/TODO.md; when none exists it asks once and defaults to ROADMAP.md. Use this skill whenever the user says "add this to the backlog", "add it to the roadmap", "plan these tasks", "break this down into tasks", "capture this as roadmap tasks", "turn these notes into a task list", or "/backlog-planner" — even if they don't name the skill. Not for executing tasks (goal-runner, task-executor, autopilot) — this writ

1 installs

Keeper Commander

Use Keeper Commander CLI and Keeper Secrets Manager workflows when installing Keeper tooling, setting up profiles, signing in, running Keeper interactively,...

Process Interviewer

Interview users before automating, documenting, or turning workflows into reusable systems.

4 installs1 stars

ProcessPlan

ProcessPlan (processplan.com). Use this skill for ANY ProcessPlan request — reading, creating, and updating data. Whenever a task involves ProcessPlan, use this skill instead of calling the API directly.

1 installs

project-doc

Create or maintain a PROJECT.md source-of-truth doc for any project, quiz-first with project-type branches. Use only when the user explicitly asks for project documentation.

1 stars