甩手掌柜技能包和工作流，适用于具备基础编程能力的技术小白使用Claude Code / Cursor / Codex / Antigravity (如果还有人用的话）等 AI 编程工具开发复杂应用。
- 鸡毛蒜皮也来问你 → 用决策策略和阈值设置，让它自主处理不重要的选择
- 按下葫芦浮起瓢，BUG越改越多 → 用改动前理解、逐文件验证、失败回退三重机制切断级联故障
- 禁止AI摸鱼 → 用 guardrail 强制要求有 diff 才能说完成、有证据才能说成功
- 屎山越堆越高 → 用健康标准和定期BUG扫描，在问题还小的时候发现它
- 看不懂技术报告 → 所有汇报强制翻译为中文产品语言
- 需求说不清楚 → 用场景化提问帮你把模糊想法变成可执行需求
- 对话之间上下文丢失 → 自动写交接备忘，下次接着干
- 功能做完不知道对不对 → 从用户角度验收，不懂代码也能判断
Hands-off-Manager/
├── README.md
├── CLAUDE.md ← 复制到项目根目录
├── guardrails/
│ └── guardrails.md ← 6 条强制约束
└── skills/
├── P0/ ← 核心，立即启用
│ ├── default-decision-policy/ 何时自主决策、何时问人
│ ├── bounded-change-planning/ 限制每次改动的范围
│ ├── evidence-based-change-report/ 完成报告 + 审计清单
│ ├── escalation-thresholds/ 升级决策纯查表
│ └── requirement-clarification/ 模糊想法 → 可执行需求
├── P1/ ← 第二批启用
│ ├── regression-watchlist/ 高风险模块检查清单 *
│ ├── surgical-refactor/ 修 bug 与重构分离
│ └── product-qa/ 从用户角度验收功能
├── communication/ ← 沟通层
│ ├── plain-language-reporting/ 所有输出翻译为中文产品语言
│ └── session-handoff/ 对话间的上下文交接
└── maintenance/ ← 代码健康
├── code-health-standards/ 好代码的定义 *
└── code-debt-cleanup/ 定期健康扫描与债务报告
* 标记的 skill 是项目模板，需要根据你的项目自定义后才能生效。
- 已安装 Claude Code（VS Code 扩展或 CLI 版本均可）
- 或使用其他支持
.claude/skills/目录的 AI 编程工具
git clone https://github.com/LinyingL/Hands-off-Manager.git
cd Hands-off-Manager
# 复制所有 skills
cp -r skills/P0/* ~/.claude/skills/
cp -r skills/P1/* ~/.claude/skills/
cp -r skills/communication/* ~/.claude/skills/
cp -r skills/maintenance/* ~/.claude/skills/
# 复制 guardrails
mkdir -p ~/.claude/rules
cp guardrails/guardrails.md ~/.claude/rules/
# 复制 CLAUDE.md 到你的项目根目录
cp CLAUDE.md /your/project/root/CLAUDE.md只安装 P0 + communication（解决最痛的 5 个问题）：
cp -r skills/P0/* ~/.claude/skills/
cp -r skills/communication/* ~/.claude/skills/
mkdir -p ~/.claude/rules
cp guardrails/guardrails.md ~/.claude/rules/
cp CLAUDE.md /your/project/root/CLAUDE.md# 确认 skills 已安装（应该看到 12 个 skill 文件夹）
ls ~/.claude/skills/
# 确认 guardrails 已安装
head -5 ~/.claude/rules/guardrails.md
# 确认 frontmatter 生效（应该以 --- 开头）
head -3 ~/.claude/skills/default-decision-policy/SKILL.md在 Claude Code 里输入 / 确认 skill 出现在补全列表里。
以下两个 skill 包含项目模板，需要根据你的实际项目修改后才能生效：
-
regression-watchlist — 打开
~/.claude/skills/regression-watchlist/SKILL.md，将模板中的示例路径和测试命令替换为你项目的实际模块。 -
code-health-standards — 打开
~/.claude/skills/code-health-standards/SKILL.md，将项目结构模板替换为你项目的实际目录布局和命名约定。
default-decision-policy — 自主决策规则。Agent 遇到未指定的选择（命名、文件组织、代码风格等）时自动触发。核心原则：跟着项目现有惯例走，没有就选更简单的。
bounded-change-planning — 改动范围控制。写代码之前自动触发，要求先产出改动计划。预算上限：3 新文件 / 8 改动文件 / 300 行 diff / 1 新依赖 / 2 新抽象。超出则停下重新规划。
evidence-based-change-report — 完成报告。每次声称完成时触发，按固定格式汇报：改了什么、为什么、跟计划有无偏差、验证证据、合规自查表。
escalation-thresholds — 升级查表。一张三级表：永远不问 / 必须问 / 有条件问。减少无意义打断，保证关键决策不被跳过。
requirement-clarification — 需求澄清。收到模糊需求时触发，用场景化问题（不是技术术语）帮你理清需求，产出中文需求确认文档后才开始写代码。
regression-watchlist — 高风险模块检查清单。列出每个区域的不变量和必跑测试。需要自定义。
surgical-refactor — 修 bug 与重构分离。五条硬规则：分开提交、一次一个概念、先删后抽象、先证明行为再改结构、不顺手改。
product-qa — 产品验收。从用户角度逐步验证：正常流程、异常情况、范围确认。产出中文验收报告。
plain-language-reporting — 中文产品语言。所有面向人的输出自动翻译，附术语翻译表（diff → 改动内容、migration → 数据库结构变更等），技术细节折叠到底部。
session-handoff — 会话交接。对话结束时自动写交接备忘：进度、决策、已知问题、约定。下次新对话自动读取。
code-health-standards — 代码质量标准。定义模块边界、命名规则、反债务规则、健康指标。需要自定义。
code-debt-cleanup — 定期健康扫描。轻量扫描（一行报告）+ 全量扫描（中文健康报告：红黄绿三级 + 趋势追踪）。
写入 .claude/rules/ 目录，始终生效。Skills 是指导，Guardrails 是硬约束：
| # | 名称 | 规则 | 触发时机 |
|---|---|---|---|
| G1 | no-diff-no-done | 没改动不能说完成 | 声称完成代码改动时 |
| G2 | no-evidence-no-success | 没证据不能说成功 | 声称代码正确时 |
| G3 | size-budget-check | 超预算强制停下 | 新文件 >3 / 改动文件 >8 / diff >300 行 |
| G4 | understand-before-modify | 改前必须理解 | 修改任何现有文件前 |
| G5 | verify-after-each-file | 改一个验一个 | 任务涉及 2+ 个文件时 |
| G6 | revert-before-retry | 两次失败回退重来 | 修复尝试连续失败时 |
- Phase 1 — 文档约束：把 guardrails.md 放入
.claude/rules/，Agent 自我遵守，你审查合规表 - Phase 2 — 验证脚本：guardrails.md 底部附了
verify-diff.sh和check-budget.sh示例脚本 - Phase 3 — CI 集成：将脚本接入 pre-commit hook 或 CI pipeline
本仓库不替代 Superpowers，而是补充它没覆盖的部分：
| 维度 | Superpowers 提供的 | 本仓库补充的 |
|---|---|---|
| 干活范围 | Writing Plans | bounded-change-planning + G3 |
| 完成标准 | Verification Before Completion | evidence-based-change-report + G1/G2 |
| 调试方法 | Systematic Debugging | surgical-refactor + G5/G6 |
| 沟通方式 | (假设使用者是开发者) | plain-language-reporting |
| 决策边界 | (无) | default-decision-policy + escalation-thresholds |
| 输入质量 | (无) | requirement-clarification |
| 跨会话 | (无) | session-handoff |
| 验收 | (无) | product-qa |
- Superpowers 原版能力全部保留，不重复造轮子
- Skills 是指导，Guardrails 是约束，两者配合使用
- 所有面向人的输出都是中文，技术细节折叠备查
- 每个 SKILL.md 带 YAML frontmatter，支持自动发现和触发
- 活文档，Agent 可以提议更新（需人类批准）
有基础编程能力但不是每天看代码的人——产品经理、创始人、项目负责人。所有报告、决策升级、健康检查都用中文产品语言。但三个环节仍需懂代码的人定期介入：需求澄清的技术细节、关键技术选型、独立代码审查。
Skills & guardrails for AI coding agents. Built for non-developers (product managers, founders, project leads) who use Claude Code / Cursor / Codex / Antigravity to build complex applications.
- Agent asks about every trivial choice → Decision policy + escalation thresholds let it handle low-stakes decisions autonomously
- Cascading bugs — fix one, break two → Understand-before-modify, verify-after-each-file, revert-before-retry — three guardrails that cut the chain
- Claims "done" without actually changing anything → Guardrails require actual diffs before "done" and evidence before "works"
- Growing code mess → Health standards + periodic debt scans catch problems while they're still small
- Can't understand technical reports → All reports auto-translated to plain product language
- Vague requirements → Scenario-based questions turn fuzzy ideas into actionable specs
- Context lost between sessions → Auto-written handoff memo, next session picks up where you left off
- Can't tell if a feature actually works → User-perspective acceptance testing — no code knowledge needed
Each skill has two versions:
SKILL.md— Chinese (default): reports, templates, and QA output in Chineseen/SKILL.md— English: same logic, English output
To use the English versions, copy the en/SKILL.md files instead:
# Example: install English version of a skill
cp skills/default-decision-policy/en/SKILL.md ~/.claude/skills/default-decision-policy/SKILL.md- Claude Code installed (VS Code extension or CLI)
- Or any AI coding tool that supports
.claude/skills/
git clone https://github.com/LinyingL/Hands-off-Manager.git
cd Hands-off-Manager
# Copy all skills (Chinese version — for English, use en/SKILL.md from each skill folder)
cp -r skills/P0/* ~/.claude/skills/
cp -r skills/P1/* ~/.claude/skills/
cp -r skills/communication/* ~/.claude/skills/
cp -r skills/maintenance/* ~/.claude/skills/
# Copy guardrails
mkdir -p ~/.claude/rules
cp guardrails/guardrails.md ~/.claude/rules/
# Copy CLAUDE.md to your project root
cp CLAUDE.md /your/project/root/CLAUDE.md/plugin marketplace add LinyingL/Hands-off-Manager
/plugin install hands-off-manager@hands-off-manager
Two skills contain project templates — customize them for your project:
- regression-watchlist — Replace example paths and test commands with your actual modules
- code-health-standards — Replace the project structure template with your actual directory layout
default-decision-policy— Autonomous decision rules. Follow existing conventions; if none, pick the simpler option.bounded-change-planning— Change plan required before coding. Budget: 3 new files / 8 modified / 300 diff lines.evidence-based-change-report— Completion report with file list, diffs, verification evidence, and compliance checklist.escalation-thresholds— Three-tier lookup table: never ask / always ask / conditional.requirement-clarification— Scenario-based questions to turn vague requests into confirmed specs before coding starts.
regression-watchlist— High-risk module checklist with invariants and required tests. Needs customization.surgical-refactor— Five rules: separate fix from refactor, one concept per task, delete before abstract.product-qa— User-perspective acceptance testing: normal flow, edge cases, scope check.
plain-language-reporting— Translates all output to plain product language. Tech details collapsed at bottom.session-handoff— Auto-writes handoff memo at session end: progress, decisions, known issues, conventions.
code-health-standards— Module boundaries, naming rules, anti-debt patterns, health metrics. Needs customization.code-debt-cleanup— Lightweight scan (one-line note) + full scan (health report with severity + trends).
Loaded into .claude/rules/, always active. Skills guide; guardrails enforce:
| # | Name | Rule | Trigger |
|---|---|---|---|
| G1 | no-diff-no-done | No changes = can't claim done | When claiming code changes complete |
| G2 | no-evidence-no-success | No evidence = can't claim success | When claiming code is correct |
| G3 | size-budget-check | Over budget = must stop and re-plan | New files >3 / modified >8 / diff >300 lines |
| G4 | understand-before-modify | Must understand before modifying | Before modifying any existing file |
| G5 | verify-after-each-file | Verify after each file change | When task touches 2+ files |
| G6 | revert-before-retry | Two failures = revert and restart | When fix attempts fail consecutively |
People with basic programming knowledge who don't read code daily — product managers, founders, project leads. All reports, escalations, and health checks use plain product language. Three areas still need a developer's periodic input: technical details in requirement clarification, key architecture decisions, and independent code review.