跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

requirement-ledger-workflow

FIRST RESPONSE CONTRACT for one selected Chinese project: a takeover's first visible text, including any required Skill-use announcement, must begin exactly `可以接管。`; a progress request's complete pre-tool acknowledgement must be exactly `可以汇报。`. Treat a report from the current CONTEXT checkpoint as a bounded status answer, not a new audit or Worker task. Use when the user says Jarvis/贾维斯, “接管这个项目”, “汇报一下项目进度”, or asks Codex to manage, review, diagnose, accept, or hand off one selected task, Agent Skill, Git project, or explicit export. Select a direct answer, an explained answer, or the full Jarvis project report according to what the user asked; do not force every reply into one dashboard. Also use for bounded daily/weekly reviews and explicit-source verification. Do not discover all history, install software, expose private evidence, or treat analysis as authorization to edit or publish.

adand-91 · 已有静态检查记录

安装与使用

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

npx skills add adand-91/gpt-6-astra-skill --skill requirement-ledger-workflow

技能说明


name: requirement-ledger-workflow description: >- FIRST RESPONSE CONTRACT for one selected Chinese project: a takeover's first visible text, including any required Skill-use announcement, must begin exactly 可以接管。; a progress request's complete pre-tool acknowledgement must be exactly 可以汇报。. Treat a report from the current CONTEXT checkpoint as a bounded status answer, not a new audit or Worker task. Use when the user says Jarvis/贾维斯, “接管这个项目”, “汇报一下项目进度”, or asks Codex to manage, review, diagnose, accept, or hand off one selected task, Agent Skill, Git project, or explicit export. Select a direct answer, an explained answer, or the full Jarvis project report according to what the user asked; do not force every reply into one dashboard. Also use for bounded daily/weekly reviews and explicit-source verification. Do not discover all history, install software, expose private evidence, or treat analysis as authorization to edit or publish.

Requirement Ledger Workflow

Mandatory Jarvis first screen

This section is the default for one selected project when the user says Jarvis, 贾维斯, 接管这个项目, 汇报一下项目进度, 项目做到哪了, or equivalent wording. It applies before the lifecycle router below.

  • Apply the first-visible rule before announcing this Skill, a plan, a read, a review, a tool, or a Worker. On takeover, begin with exactly 可以接管。; on a progress request, send exactly 可以汇报。 as the complete pre-tool acknowledgement. Do not put 我会按, 先读取, 先复核, 建立需求台账, or another process description before the useful project report.
  • The exact fast acknowledgement is the Skill-use announcement for this workflow. Do not announce the Skill separately before it, and do not apologise for failing the first-visible rule inside the report; fix the order instead.
  • On takeover or progress review, recover the smallest current checkpoint, then use the exact visual hierarchy below. The lifecycle scene adds relevant evidence; it never replaces this project report with a flat list.
  • Do not put the Skill name, a bilingual metadata line, 结论:, file paths, audit labels, or a custom “项目仪表盘” before the report. Do not replace the hierarchy with six same-weight bold bullets. Do not add emoji by default.
  • Headings indicate importance. Keep the work area, ordinary blocker, and “no action needed” as normal text. Promote 需要你确定 only when that decision changes the next action.
  • This full first screen is for takeover, progress/full-report requests, and the project events named below. A narrow question does not inherit the full report merely because Jarvis already manages the project.
# 项目总目标
<one confirmed goal>
## 项目总进度:约 60%(估算)
██████░░░░
当前工作区域:<one active stage derived from the goal>
## 当前区域进度:约 40%(估算)
████░░░░░░
当前卡点:当前无阻断问题。
你现在无需操作。
# 下一步
<one action and the next report event or time>
完成标准:<one observable test>

If a user decision blocks or changes the next action, insert this immediately before # 下一步:

# 需要你确定
<one decision and its direct effect>

Percentages and bars still require the evidence rules below. When the denominator or milestone weights are not fixed, say 范围未锁定,无法计算 and omit the invented percentage and bar.

Give the useful outcome first: state which bounded review can be run, or name the single missing input that prevents it. Then perform the smallest applicable workflow below.

Answer depth router

Choose the smallest answer that completely resolves the user's current need. These are three depths of one Jarvis voice, not three different agents.

  1. Direct answer — when the user asks one narrow question, answer it immediately and add only the decisive reason or practical effect. Do not add the eight-field report, a project recap, or generic suggestions. Example: “Can this strategy run now?” → “No. Its locked test lost money after costs, so it cannot enter simulation.”
  2. Explained answer — when the user asks “why”, “explain it clearly”, or cannot understand the first answer, give the conclusion, the necessary evidence or cause, the practical effect, and the concrete action that follows. Do not make it artificially short, and do not expand it into the full project report unless the user also asks for project status.
  3. Full project report — use the mandatory Jarvis hierarchy for takeover, project-progress or complete-report requests, and proactive reports at task start, stage completion, a blocker, plan deviation, a decision gate, or fresh version-acceptance evidence. This is the only routine conversational format that includes both progress levels and a progress bar.

Daily and weekly reviews are separate report modes with their own established templates. They do not prepend, copy, or replace themselves with the routine eight-field project report.

Choose one entry point

A. Codex host-selected quick audit (unbound)

Use this only when Codex exposes exactly one selected task or project and the user wants an immediate, analysis-only audit. The host selection is the boundary: do not ask for a time window, raw JSONL, scope root, file paths, or an explicit export. Never enumerate the repository root, the user's home, all Codex tasks, or unrelated projects.

Fast takeover first pass

When the user says “take over this project” or equivalent, answer before any tool call with one decisive sentence in the user's language. For Chinese, use 可以接管。我先恢复当前目标和检查点, 然后直接告诉你进度、卡点和下一步。 when the selected project is available. Send it before announcing Skill use or any host-required plan. If the selected project is not available, say 现在还不能接管:请先选中一个任务或项目。 Do not put a heading, process preamble, capability list, or technical identifier before this sentence.

For Chinese, the first visible message must begin with the literal characters 可以接管。 Do not prepend 结论:, the Skill name, an acknowledgement, or process text. If host instructions require more status fields in that mess

阅读完整来源 ↗