harness-build-core-manifest
Skill0 starsChanged 8 months agoMITView on GitHub
构建≤60行的核心规则清单,从源头避免Agent行为跑偏
In this repository33 other files it gives its agents.
- harness-10x-productivity-boostSkill
- harness-adjust-granularitySkill
- harness-analyze-project-scaleSkill
- harness-auto-full-executionSkill
- harness-brainstormSkill
- harness-build-context-indexSkill
- harness-build-deterministic-workflowSkill
- harness-check-clean-stateSkill
- harness-configSkill
- harness-context-clearSkill
- harness-determine-granularitySkill
- harness-diagnose-and-improveSkill
- harness-enable-circuit-breakerSkill
- harness-enforce-architecture-guardrailsSkill
- harness-escalate-to-humanSkill
- harness-evaluate-performanceSkill
- harness-evolveSkill
- harness-executing-plansSkill
- harness-generate-feature-listSkill
- harness-goalSkill
- harness-handle-failureSkill
- harness-initSkill
- harness-merge-agent-resultsSkill
- harness-merge-subharness-resultSkill
- harness-monitor-agent-batchSkill
- harness-monitor-subharness-agentSkill
- harness-planSkill
- harness-recover-clean-stateSkill
- harness-schedule-parallel-agentsSkill
- harness-session-handoffSkill
- harness-spawn-subharness-agentSkill
- harness-track-feature-progressSkill
- harness-validate-outputSkill
The file
Files
harness-build-core-manifest 构建核心规则清单
核心能力
- 检查 harness-init 是否完成
- 创建 AGENTS_MANIFEST.md(≤60行)
- 定义架构分层规则
- 定义命名规范
- 定义PR合并要求
前置条件
- harness-init 已完成
- .EnjoyHarness/GLOBAL_STATE.md 存在
执行步骤
Step 1: 检查前置条件
使用 Read 工具读取:.EnjoyHarness/GLOBAL_STATE.md
检查条件:
- 文件存在
- status: active
如果未初始化:
❌ 错误: 系统未初始化
💡 请先运行: harness-initStep 2: 创建 AGENTS_MANIFEST.md
使用 Write 工具创建文件:AGENTS_MANIFEST.md
内容(≤60行):
# AGENTS_MANIFEST - 核心规则清单
## 架构分层规则(7条)
1. Types → Config → Repo → Service → Runtime → UI
2. 每层仅依赖直接下层
3. 禁止跨层调用
4. 公共接口必须在 Types 层
5. 配置必须在 Config 层
6. 业务逻辑在 Service 层
7. UI 仅处理展示逻辑
## 命名规范(6条)
1. 技能命名: harness-{verb}-{target} 或 harness-{noun}
2. 文件命名: 小写+连字符 (harness-init.md)
3. 目录命名: 小写+连字符 (skills/harness-init/)
4. 状态文件: 大写+下划线 (GLOBAL_STATE.md)
5. Manifest 文件: {NAME}_MANIFEST.md
6. Git 分支: feature/{task-id} 或 fix/{task-id}
## PR合并要求(5条)
1. 所有测试必须通过
2. 代码覆盖率 ≥ 80%
3. 无架构违规(通过 harness-enforce-architecture-guardrails)
4. 无高危安全漏洞
5. 至少 1 个 reviewer 批准
## 迭代限制(2条)
1. 最大迭代次数: 100次(可配置)
2. 熔断机制: 迭代次数≥100 → 强制停止
## 错误处理(3条)
1. 同一任务失败≥3次 → 停止尝试
2. 系统级错误 → 进入真实阻塞升级链路
3. 所有操作必须留痕到 EVENT_LOG.md
总计: 23条核心规则(≤60行)Step 3: 更新事件日志
使用 Edit 工具追加内容到:.EnjoyHarness/EVENT_LOG.md
追加内容:
2026-03-28T10:45:00+08:00 | SKILL_START | harness-build-core-manifest | 开始构建核心规则 | SUCCESS
2026-03-28T10:45:00+08:00 | SKILL_COMPLETE | harness-build-core-manifest | 核心规则构建完成 | SUCCESSStep 4: 更新事件计数
使用 Edit 工具更新:.EnjoyHarness/EVENT_LOG.md
old_string: total_events: 2
new_string: total_events: 4
Step 5: 更新技能注册表
使用 Edit 工具更新:.EnjoyHarness/SKILL_REGISTRY.md
old_string: - [ ] harness-build-core-manifest - 构建核心规则技能
new_string: - [x] harness-build-core-manifest - 构建核心规则技能 ✅
Step 6: 输出完成信息
使用 Bash 工具输出:
echo ""
echo "✅ harness-build-core-manifest 完成!"
echo ""
echo "📋 核心规则文件:"
echo " - AGENTS_MANIFEST.md"
echo ""
echo "📊 规则统计:"
echo " - 架构分层规则: 7条"
echo " - 命名规范: 6条"
echo " - PR合并要求: 5条"
echo " - 迭代限制: 2条"
echo " - 错误处理: 3条"
echo " - 总计: 23条核心规则"
echo ""
echo "🎯 下一步:"
echo " 运行 harness-build-context-index 完成上下文索引构建"
echo ""成功标准
- AGENTS_MANIFEST.md 文件存在
- 文件行数 ≤ 60行
- 规则条数 ≤ 25条
- 无模糊表述(所有规则可验证)
- 技能注册表已更新
失败兜底
- harness-init 未完成 → 终止执行,提示运行 harness-init
- 文件创建失败 → 记录错误到 EVENT_LOG.md,触发重试
联动关系
- 前置: harness-init
- 自动触发: harness-build-context-index, harness-enforce-architecture-guardrails
迭代计数
本技能执行预计迭代次数: 约 5 次(Write 1次 + Edit 3次 + Read 1次)
测试用例
测试 1: 前置条件检查
输入: 在未初始化的系统运行 期望输出: 错误提示"系统未初始化" 验证方式: 删除 GLOBAL_STATE.md 后运行
测试 2: 文件行数验证
输入: 执行 harness-build-core-manifest
期望输出: AGENTS_MANIFEST.md ≤ 60行
验证方式: wc -l AGENTS_MANIFEST.md
测试 3: 规则完整性
输入: 读取 AGENTS_MANIFEST.md
期望输出: 包含架构分层、命名规范、PR合并要求
验证方式: grep -c "条$" AGENTS_MANIFEST.md
测试 4: 技能注册表更新
输入: 读取 SKILL_REGISTRY.md
期望输出: harness-build-core-manifest 标记为完成
验证方式: grep "harness-build-core-manifest" .EnjoyHarness/SKILL_REGISTRY.md
测试 5: 事件日志记录
输入: 读取 EVENT_LOG.md
期望输出: 包含 harness-build-core-manifest 启动和完成事件
验证方式: grep "harness-build-core-manifest" .EnjoyHarness/EVENT_LOG.md
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
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.

