@crisxuan/agent-workflow-kit
BEvaluation-first workflow rules for bringing AI coding agents into real software projects.
Install
agr install @crisxuan/agent-workflow-kit --target codexWrites 1 file into AGENTS.md, pinned to git-1b00a95d.
- AGENTS.md
Document
AI Project Workflow
Project Rules
This is a public documentation and agent-workflow repository. Keep changes focused, readable, and tool-neutral.
Before editing, inspect the existing structure and follow local patterns. Do not introduce unrelated formatting churn, broad rewrites, or new tooling unless the change needs it.
Synchronization Requirements
When changing public guide content, keep these pairs synchronized:
README.mdandREADME.zh-CN.mddocs/guide.mdanddocs/guide.zh-CN.mdskills/agent-workflow-kit/andskills/agent-workflow-kit-zh-cn/
When changing reusable workflow rules or references, check whether the same idea appears in:
docs/guide*.mdskills/*/SKILL.mdskills/*/references/agents-templates*.mdskills/*/references/engineering-references*.md
Do not leave one language or package with stale references that were removed elsewhere.
Verification
Before completion, run:
ruby scripts/check-docs.rb
git diff --check
For faster local structural checks, or when network link checks are flaky, run:
SKIP_LINK_CHECK=1 ruby scripts/check-docs.rb
External Action Safety
Ask before changing GitHub repository metadata, topics, releases, branch settings, Pages settings, or other remote configuration.
Ask before pushing commits unless the user explicitly requests a push.
Completion Criteria
A task is complete only when:
- the requested documentation or workflow change is implemented
- related English and Chinese files are synchronized
- related guide and skill references are synchronized
- verification commands pass, or failures are clearly explained
- the final response reports what changed and what was verified
Repository README
Describes crisxuan/agent-workflow-kit as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.
Agent Workflow Kit
Evaluation-first workflow rules for bringing AI coding agents into real software projects.
English Guide · 中文文档 · 中文首页
What This Is
Agent Workflow Kit is a tool-neutral guide and agent workflow package for deciding whether a repository needs AI-assisted development rules, and how heavy those rules should be. It is not tied to Codex: any LLM, coding agent, or agent harness can use the guide, templates, and rules.
It helps maintainers answer five practical questions:
- Does this project need an AI workflow at all?
- Should the workflow be minimal, standard, or full?
- When should a spec layer be used?
- What should AI agents verify before claiming work is done?
- Which external actions require explicit maintainer approval?
The central rule is simple:
Evaluate the project first. Then choose the smallest workflow that reduces real risk.
At A Glance
flowchart LR
Inspect["Inspect repo"]
Score["Score risk<br/>0-16"]
Level["Choose level<br/>0 / 1 / 2 / 3"]
Rules["Copy rules<br/>AGENTS.md"]
Verify["Verify on<br/>one small change"]
Inspect --> Score --> Level --> Rules --> Verify
Why Use It
| Problem | What This Project Provides |
|---|---|
| AI agents jump into code too quickly | A repo inspection and risk scoring flow before changes |
| Requirements vanish into chat history | Guidance for adding a spec or change-memory layer only when needed |
| Work is claimed done without evidence | Copy-ready verification and completion rules for AGENTS.md |
| Tooling stacks overlap and conflict | Conflict rules for specs, plans, reviews, hooks, and external actions |
| Teams want consistent agent behavior | Agent-facing Skill packages and reusable templates for repeatable evaluations |
How To Use The Kit
| Path | Best When |
|---|---|
| Read the English guide or Chinese guide | You want to evaluate a project manually |
| Copy examples/AGENTS.level-2.md | You want a practical standard workflow starter |
Use the skills/agent-workflow-kit package | You want an agent to inspect a repo and produce a workflow decision |
| Adapt the Markdown rules for Claude, Cursor, Codex, Gemini, or another harness | You want consistent behavior across tools |
Quick Start
- Open the English guide or Chinese guide.
- Score your project with the 0-16 risk table.
- Choose the matching workflow level.
- Copy the smallest useful
AGENTS.mdtemplate block. - Fill in real install, test, lint, build, and browser/E2E commands.
- Test the workflow on one small change before making it team policy.
Workflow Levels
| Level | Use When | Typical Rules |
|---|---|---|
| Level 0 | AI does not edit code, or the project is disposable | No formal AI workflow |
| Level 1 | Small maintained projects | Basic agent rules and verification commands |
| Level 2 | Most AI-assisted software projects | Basic rules, spec guidance, agent discipline, external-action safety |
| Level 3 | Production, security-sensitive, complex UI, or multi-agent teams | Level 2 plus review gates and stronger verification |
Documentation
| Document | Purpose |
|---|---|
| English Guide | Full public guide for maintainers |
| Chinese Guide | Full Chinese public guide |
| AGENTS Templates | Copy-ready English AGENTS.md blocks |
| 中文 AGENTS 模板 | Copy-ready Chinese Skill reference with English agent blocks |
| Engineering References | Optional engineering guideline catalog |
| 中文工程规约参考 | Chinese reference catalog |
| Contributing | Contribution and synchronization guide |
| Changelog | Project change history |
| Level 2 AGENTS Example | Copy-ready standard workflow starter |
Agent Skills And Templates
The skills/ directory contains agent-facing versions of the guide. They are packaged as Codex-compatible Skills, but the instructions are plain Markdown and YAML, so other LLMs, coding agents, and agent harnesses can read and adapt them as project workflow rules.
These packages are optional. If you only want the human guide or AGENTS.md templates, use the documents above.
| Skill | Use It For |
|---|---|
skills/agent-workflow-kit | English agent Skill package for evaluating a repository, scoring risk, recommending workflow level, and preparing project rules after approval |
skills/agent-workflow-kit-zh-cn | Chinese agent Skill package with the same workflow and Chinese-facing instructions |
Each skill includes:
SKILL.md: the agent workflow and safety rulesagents/openai.yaml: display metadata and default promptreferences/agents-templates*.md: reusableAGENTS.mdtemplate blocksreferences/engineering-references*.md: optional engineering reference catalog
Example prompts:
Use $agent-workflow-kit to evaluate this repository and recommend the right AI workflow level.
使用 $agent-workflow-kit-zh-cn 评估这个仓库,并推荐合适的 AI 工作流级别。
Repository Layout
README.md # Project homepage
README.zh-CN.md # Chinese project homepage
AGENTS.md # AI maintenance rules for this repo
CONTRIBUTING.md # Contribution guide
CHANGELOG.md # Project change history
.gitattributes # GitHub Linguist metadata
docs/guide.md # Full English guide
docs/guide.zh-CN.md # Full Chinese guide
examples/AGENTS.level-2.md # Copy-ready standard workflow starter
skills/
agent-workflow-kit/ # English agent Skill package
agent-workflow-kit-zh-cn/ # Chinese agent Skill package
scripts/check-docs.rb # Markdown, YAML, skill, and link checks
.github/workflows/docs-check.yml # GitHub Actions validation
Validation
Run the local checks before publishing documentation changes:
ruby scripts/check-docs.rb
The check validates Markdown fences, YAML syntax, skill structure, and public links.
License
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-1b00a95d6ed92026-08-04