agentleFS
arcobaleno64arcobaleno64/council-forge/template/AGENTS.md

council-forge / template

AGENTS.md0 starsChanged 6 months agoMITView on GitHub

本檔案是 artifact-first multi-agent workflow 的文件索引。每個 agent 只需載入自己的入口檔 + 當前階段所需的參考文件。

The file

Files
AGENTS.md

AGENTS -- 文件索引

本檔案是 artifact-first multi-agent workflow 的文件索引。每個 agent 只需載入自己的入口檔 + 當前階段所需的參考文件。

Agent 入口檔

Agent入口檔角色自動載入
Claude CodeCLAUDE.md協調者Yes (project instruction)
Gemini CLIGEMINI.md研究與 read-only memory curatorYes (passed via prompt)
Codex CLICODEX.md實作主責Yes (passed via prompt)

文件模組

File用途~Tokens載入時機
docs/orchestration.md系統提示骨幹:目標、原則(§1-§2.8)1100Claude:session 開始
docs/orchestration-workflow.mdworkflow/gate/PDCA 細節與 sync contract(§3+)1400Claude:流程與 gate 判定前
docs/artifact_schema.mdschema 入口與通用規則(§1-§4 + §5索引)900寫任何 artifact 前
docs/schemas/artifact-spec-task.mdTask schema(原 §5.1)450撰寫 task artifact 前
docs/schemas/artifact-spec-research.mdResearch schema(原 §5.2)650撰寫 research artifact 前
docs/schemas/artifact-spec-plan.mdPlan schema(原 §5.3)550撰寫 plan artifact 前
docs/schemas/artifact-spec-code.mdCode schema(原 §5.4)900撰寫 code artifact 前
docs/schemas/artifact-spec-test.mdTest schema(原 §5.5)350撰寫 test artifact 前
docs/schemas/artifact-spec-verify.mdVerify schema(原 §5.6)800撰寫 verify artifact 前
docs/schemas/artifact-spec-decision.mdDecision schema(原 §5.7)700撰寫 decision artifact 前
docs/schemas/artifact-spec-status.mdStatus schema(原 §5.8)500更新 status artifact 前
docs/schemas/artifact-gallery.md跨類型範例集(源自 §5)250需要快速對照範例時
docs/subagent_roles.md角色責任敘述(§1, §3-§9)2200派發 subagent 前
docs/raci-matrix.mdRACI 與 capability 矩陣(原 §2)900派發 subagent 前
docs/workflow_state_machine.md8 個狀態 + 合法轉移600狀態轉移前
docs/premortem_rules.md風險分析格式 + 品質護欄1900進入 coding gate 前
docs/red_team_runbook.md紅隊演練 runbook:靜態攻擊、live drill、復盤流程1500紅隊演練前
docs/red_team_scorecard.md紅隊演練評分矩陣與總結判定900演練記錄與復盤時
docs/red_team_backlog.md紅隊演練後續補強清單700復盤 / 補強規劃時
docs/subagent_task_templates.mdTemplate 索引(指向 docs/templates/)200派發 subagent 時
docs/templates/<role>/TEMPLATE.md各角色 prompt 範本(含 YAML frontmatter)每個 ~150派發對應 subagent 時
artifacts/scripts/discover_templates.pyTemplate auto-discovery CLI200派發 subagent 前
docs/lightweight_mode_rules.md小任務精簡流程規則350lightweight mode 任務時

Markdown 書寫語言規範

  • 長期維護的 Markdown 文件以繁體中文(臺灣)為主。
  • 專有名詞、檔名、CLI 指令、環境變數、artifact type、狀態值、placeholder、schema literal 保留英文原字。
  • 不得更動會被 agent、validator、腳本依賴的精確字串,例如 ## Metadata、Task ID、Artifact Type、Owner、Status、Last Updated 與各種狀態值。
  • 所有規範中的紀錄時間、Last Updated 與相關時間戳,一律使用 Asia/Taipei,採 ISO 8601 並帶 +08:00。
  • source template repo(含 .council-forge-source-repo)中,root、template/ 與 Obsidian 入口文件必須保持語義一致;由 template/ 複製出的 downstream terminal repo 不再建立新的 template/,只維護 root 文件與 OBSIDIAN.md。
  • GitHub 對外入口以 README.md / README.zh-TW.md 為準;Obsidian 入口以 OBSIDIAN.md 為準。
  • 歷史 artifacts、實驗輸出、外部 repo 內 Markdown 不在追溯改寫範圍內。

階段載入矩陣

階段PDCA 階段Claude Code 載入Gemini 載入Codex 載入
IntakeP (pre-Plan)docs/orchestration.md----
ResearchP (Plan 前準備)docs/subagent_roles.md §4, docs/subagent_task_templates.md, docs/templates/(GEMINI.md has all needed rules)--
PlanningP (Plan,含 premortem)docs/schemas/artifact-spec-plan.md §5.3, docs/workflow_state_machine.md, docs/premortem_rules.md----
CodingD (Do;微觀內含 TAO)docs/subagent_roles.md §5, docs/subagent_task_templates.md, docs/templates/--(CODEX.md has all needed rules)
VerificationC (Check)docs/schemas/artifact-spec-test.md §5.5 + docs/schemas/artifact-spec-verify.md §5.6, docs/workflow_state_machine.md----
ClosureA (Act;Gate E + 回灌)docs/workflow_state_machine.md, .github/prompts/remember-capture.prompt.mdMemory Bank Curator 模式時讀 docs/templates/memory-curator/TEMPLATE.md--
Red Team ExerciseC (Check 衍生)docs/red_team_runbook.md, docs/red_team_scorecard.md, docs/red_team_backlog.md----
Sync Contractmetadocs/orchestration-workflow.md §9----

兩層架構詳見 docs/orchestration.md §2.8:管理層 PDCA 對應上表「PDCA 階段」欄;執行層 TAO/ReAct 內含於 Coding 階段內 subagent dispatch(詳見 docs/agentic_execution_layer.md)。

交叉引用慣例

  • 使用 see docs/X.md §N 引用特定章節,避免重複貼內容。
  • 範例:"Research artifact format: see docs/artifact_schema.md §5.2"
  • Agent 入口檔(CLAUDE/GEMINI/CODEX.md)內嵌了 agent 無法自行額外載入時必須遵守的關鍵規則。
  • docs/ 內的參考文件由協調者(Claude Code)依階段按需載入。

章節速查

docs/artifact_schema.md

  • §1-§4 通用規則 / §5 索引

docs/schemas/*

  • artifact-spec-task.md(§5.1) / artifact-spec-research.md(§5.2) / artifact-spec-plan.md(§5.3)
  • artifact-spec-code.md(§5.4) / artifact-spec-test.md(§5.5) / artifact-spec-verify.md(§5.6)
  • artifact-spec-decision.md(§5.7) / artifact-spec-status.md(§5.8) / artifact-gallery.md

docs/subagent_roles.md

  • §3 Claude Code / §4 Gemini CLI(含 Memory Bank Curator 模式) / §5 Codex CLI / §6 Implementer / §7 Tester / §8 Verifier / §9 Reviewer

docs/premortem_rules.md

  • §1-2 When & where / §3 Required fields / §4 Quality rules (P1-P8) / §5 Violation levels / §6 Minimum counts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.