跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

project-flow

Use when deciding what step a piece of work is at or what comes next, when starting work on an issue, when a pull request has merged, before a release, or when asked whether an issue or feature is finished or what is left.

reyxdz · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add reyxdz/going-dark --skill project-flow

技能说明


name: project-flow description: Use when deciding what step a piece of work is at or what comes next, when starting work on an issue, when a pull request has merged, before a release, or when asked whether an issue or feature is finished or what is left.

Project flow: where is this work, and what comes next?

What this skill is for

Use it to answer questions like "Is issue #12 finished?", "What is left?" or "What comes next?". You check nine steps, one at a time, give each one a status, and send a report in a fixed format.

Work is finished only when real users have it and the records say so. Merged code is not finished.

How to follow this file

  1. Do the steps in order, from Step 1 to Step 6. Do not skip a step. Do not change the order.
  2. Each step has three parts:
    • Do — what to do. Commands are shown in code blocks. Replace every <word in angle brackets> with the real value and remove the brackets.
    • Check — what must be true before you go on.
    • If not — what to do when the check fails.
  3. Never invent a fact. Every name, number, date, file path and result you write must come from something you read or ran during this task, or that the person told you. If a source gives an approximate value ("about three weeks ago"), keep it approximate and say where it came from. If a template asks for a value you do not have, write [NOT CHECKED: <what> — <why>] in its place.
  4. When you cannot do something — a command fails, you have no access to the repository or GitHub, a file does not exist — do not guess and do not pretend it worked. Write [NOT CHECKED: <what> — <why>] in your notes and go on to the next instruction. Every [NOT CHECKED] appears in the report.
  5. The project's own rules win. If a project file listed in Step 1 says something different from this file, do what the project says, and add to the report: The project's rule "<quote>" replaced this skill's rule "<quote>".
  6. This skill only reads. Do not create, edit, close, merge or comment on anything. Only report.

Words used in this file

WordMeaning
ownerThe person who decides what is built, merges pull requests and releases. Step 1 shows how to find them.
issueThe GitHub issue that describes the work, for example #12. <N> in this file means its number, without the #.
pull request (PR)A proposed change. Merged means it is in the default branch.
default branchThe branch pull requests go into, usually main. Step 1 finds it.
release branchThe branch real users get, for example production. Some projects have none: they release with tags, or deploy the default branch directly. Step 1 finds out which.
planA document, usually in docs/plans/, that splits a large issue into phases. Small issues have no plan.
phaseOne part of a plan. One pull request may deliver one phase or several, as long as it names each one it delivers.
decision record (ADR)A short document, usually in docs/decisions/ or docs/adr/, recording a choice that is expensive to undo. Its status is Proposed, Accepted or Superseded.
handoffA document telling another agent or person how to build an issue, usually in docs/handoffs/.
stagingA copy of the live site, used to try changes before real users get them.
recordsThe issue, the plan, decision records, index tables (README files listing plans, decisions or handoffs) and pull request descriptions.
closing keywordClose, Closes, Closed, Fix, Fixes, Fixed, Resolve, Resolves or Resolved, in any capitals, followed by #<N>, in a pull request description. GitHub closes the issue when that pull request merges. Part of #<N> does not close it.
replacedA pull request was closed without merging, and a later one says it replaces it ("Replaces #40"), or the owner says so.

The nine steps

Every piece of work goes through these nine steps, in this order.

#StepDone when
1IssueThe issue has a summary of the problem, a list of what to build, and a measurable "Verify" or "Done when" section.
2DecideNo open question is left on the issue. Every decision record the issue or plan names is Accepted. If the work needs more than one pull request, a plan exists.
3HandoffA handoff exists if the work was given to someone else to build.
4BuildEvery phase of the plan was delivered by a merged pull request, and no pull request for the issue is still open.
5AuditEvery merged pull request was audited before it merged.
6MergeEvery pull request for the issue is merged (or closed and replaced by one that merged).
7Verify on stagingSomeone used the change on staging — a real phone, light and dark theme, the plan's verify steps — and wrote down what they checked.
8ReleaseThe change is in what real users get.
9Close outThe plan's boxes are ticked, its status says complete, follow-up work has its own issues, and the issue is closed.

The four statuses

Give every step exactly one status.

StatusUse it when
DoneYou saw evidence that the "Done when" is true.
Not doneYou looked, and the evidence shows it is false or missing.
Not neededThe step does not apply. Only allowed where Step 3 below says so.
UnconfirmedYou could not look: no access, the command failed, or the file was not available to you. (Step 5, Audit, has its own rule below.)

The difference that matters: looked and did not find it = Not done. Could not look = Unconfirmed.

Example: you read the issue and every comment, and nobody wrote down a staging check. Step 7 is Not done. You could not open the issue at all. Step 7 is Unconfirmed.

Step 1 — Find the proje

阅读完整来源 ↗