Context, not Control
A skill that transforms how you work with AI - from micromanaging every step to providing context and letting AI make decisions. Inspired by the "Context, not Control" philosophy from the OpenClaw community.
Core Philosophy
Traditional approach: You tell AI exactly what to do, step by step.
This approach: You tell AI what you want to achieve, AI figures out how.
The key insight: AI works best when you give it rich context about your goals, constraints, and preferences - then trust it to execute within appropriate boundaries.
When to Use This Skill
- - Starting a new project with vague requirements
- Want to reduce back-and-forth and rework
- Need AI to take more initiative and make decisions
- Want to establish clear permission boundaries
- Transitioning from "micromanaging AI" to "trusting AI"
Quick Start
1. Initialize Your Context
Run the initialization script to set up your project context and permission level:
CODEBLOCK0
This creates:
- -
PROJECT.md - Your project context (goals, constraints, preferences) - INLINECODE1 - Your permission boundaries
2. Set Your Permission Level
Choose one of three levels:
Level 1 - Master Mode (Full autonomy)
- - AI makes all technical decisions
- Only confirms: spending money, public messages, deleting databases
- Best for: High trust, high risk tolerance
Level 2 - Collaborative Mode (Balanced, recommended)
- - AI executes most tasks autonomously
- Confirms: money, public messages, important deletions, system changes
- Best for: Most users, balanced control
Level 3 - Assistant Mode (High control)
- - AI provides suggestions and code
- Confirms: All operations before execution
- Best for: New users, low risk tolerance, learning mode
3. Start with Requirements
Instead of detailed specifications, start with what you want:
CODEBLOCK1
AI will ask clarifying questions:
- - Who is this for?
- What's the core use case?
- Any similar products to reference?
- Technical constraints?
- Time/budget limits?
4. Iterate and Execute
AI clarifies → You answer → AI confirms understanding → You approve → AI executes
All clarified requirements are saved to PROJECT.md for future reference.
How It Works
Requirement Clarification Framework
When you provide a vague requirement, AI uses a structured approach:
- 1. Understand the domain - What type of project is this?
- Identify the user - Who will use this?
- Clarify the goal - What problem does this solve?
- Establish constraints - Technical, time, budget limits?
- Set success criteria - What does "done" look like?
- Confirm understanding - Repeat back what you heard
See references/clarification-framework.md for detailed question templates.
Permission System
The skill automatically checks permissions before executing operations:
CODEBLOCK2
Customize your red/yellow/green lines in PERMISSION_CONFIG.yaml.
Context Management
All clarified requirements are automatically saved to PROJECT.md:
- - Project goals and constraints
- Technical stack decisions
- Success criteria
- Permission level
- Iteration history
This context is loaded in future conversations, eliminating repeated questions.
Permission Levels in Detail
Level 1: Master Mode
Philosophy: Maximum autonomy, minimum interruption
AI can do without asking:
- - Write, test, and deploy code
- Install dependencies and tools
- Modify configurations
- Create/update files
- Make architectural decisions
- Research and learn new technologies
AI must confirm:
- - Spending money (API calls, services, domains)
- Sending public messages (emails, tweets, posts)
- Deleting databases or critical data
- Restarting production services
Best for: Experienced users who trust AI and can handle mistakes
Level 2: Collaborative Mode (Default)
Philosophy: Trust but verify on important operations
AI can do without asking:
- - Write and test code
- Create/update files
- Research and documentation
- Install development dependencies
- Run tests and checks
AI must confirm:
- - Spending money
- Sending any external messages
- Deleting important files/data
- Modifying system configurations
- Restarting services
- Installing system-level packages
Best for: Most users, balanced approach
Level 3: Assistant Mode
Philosophy: AI suggests, you decide
AI can do without asking:
- - Provide suggestions and explanations
- Show code examples
- Research information
AI must confirm:
- - All file operations
- All code execution
- All installations
- All external calls
Best for: New users, learning mode, high-stakes environments
Examples
See references/examples.md for detailed examples including:
- - Building a chat application from vague requirements
- Migrating a legacy system with unclear scope
- Creating automation tools with evolving needs
See assets/EXAMPLE_DIALOG.md for sample conversations.
Customization
Custom Permission Rules
Edit PERMISSION_CONFIG.yaml to define your own boundaries:
CODEBLOCK3
Project Templates
Create custom templates in assets/ for recurring project types:
- - INLINECODE10
- INLINECODE11
- INLINECODE12
Troubleshooting
See references/troubleshooting.md for common issues:
- - AI asking too many questions
- AI not asking enough questions
- Permission checks too restrictive/loose
- Context not being saved properly
Scripts Reference
init_context.py
Initialize project context and permission config
CODEBLOCK4
clarify_requirement.py
Run requirement clarification dialogue
CODEBLOCK5
permission_check.py
Check if an operation requires confirmation
CODEBLOCK6
update_context.py
Update project context with new information
CODEBLOCK7
Philosophy: Three Modes of AI Usage
Mode 1: Paintbrush (Micromanagement)
- - You specify every detail
- AI is a tool that executes exactly what you say
- Upper limit: Your expertise
Mode 2: Employee (Delegation)
- - You assign tasks with some guidance
- AI follows your preferred patterns
- Still requires oversight
Mode 3: Master (Autonomy)
- - You set goals and constraints
- AI makes decisions and executes
- You review outcomes, not process
This skill helps you transition from Mode 1 → Mode 3 at your own pace.
Credits
Inspired by the "Context, not Control" philosophy discussed in the OpenClaw community, particularly the experiences shared by contributors who achieved remarkable results by trusting AI with more autonomy.
Version
1.0.0 - Initial release
技能名称:context-not-control
详细描述:
上下文,而非控制
一种改变你与AI协作方式的技能——从微观管理每一步,转变为提供上下文并让AI自主决策。灵感来源于OpenClaw社区的上下文,而非控制理念。
核心理念
传统方式:你一步步精确告诉AI该做什么。
本方式:你告诉AI想要实现什么目标,AI自行规划路径。
关键洞察:当你提供丰富的目标、约束和偏好上下文时,AI表现最佳——然后信任它在适当边界内执行。
何时使用本技能
- - 启动需求模糊的新项目
- 希望减少反复沟通和返工
- 需要AI更主动地决策
- 希望建立明确的权限边界
- 从微观管理AI过渡到信任AI
快速入门
1. 初始化上下文
运行初始化脚本,设置项目上下文和权限级别:
bash
python scripts/init_context.py
这将创建:
- - PROJECT.md - 项目上下文(目标、约束、偏好)
- PERMISSION_CONFIG.yaml - 权限边界
2. 设置权限级别
选择以下三个级别之一:
级别1 - 大师模式(完全自主)
- - AI做出所有技术决策
- 仅需确认:花钱、发送公开消息、删除数据库
- 适用场景:高信任度、高风险承受力
级别2 - 协作模式(平衡,推荐)
- - AI自主执行大部分任务
- 需确认:花钱、公开消息、重要删除、系统变更
- 适用场景:大多数用户,平衡控制
级别3 - 助手模式(高控制)
- - AI提供建议和代码
- 需确认:所有操作执行前确认
- 适用场景:新用户、低风险承受力、学习模式
3. 从需求开始
无需详细规格,直接说明你的需求:
我需要一个团队聊天工具
AI会提出澄清性问题:
- - 为谁开发?
- 核心使用场景是什么?
- 是否有可参考的类似产品?
- 技术约束?
- 时间/预算限制?
4. 迭代与执行
AI澄清 → 你回答 → AI确认理解 → 你批准 → AI执行
所有澄清的需求将保存到PROJECT.md中,供后续参考。
工作原理
需求澄清框架
当你提出模糊需求时,AI采用结构化方法:
- 1. 理解领域 - 这是什么类型的项目?
- 识别用户 - 谁会使用它?
- 明确目标 - 解决什么问题?
- 建立约束 - 技术、时间、预算限制?
- 设定成功标准 - 完成是什么样子?
- 确认理解 - 复述你听到的内容
详细问题模板见references/clarification-framework.md。
权限系统
本技能在执行操作前自动检查权限:
python
示例:AI想要删除文件
if permission
check(deletefile, user
permissionlevel):
# 请求用户确认
else:
# 直接执行
在PERMISSION_CONFIG.yaml中自定义红/黄/绿线。
上下文管理
所有澄清的需求自动保存到PROJECT.md:
- - 项目目标和约束
- 技术栈决策
- 成功标准
- 权限级别
- 迭代历史
这些上下文将在后续对话中加载,避免重复提问。
权限级别详解
级别1:大师模式
理念:最大自主权,最少中断
AI无需询问即可执行:
- - 编写、测试和部署代码
- 安装依赖和工具
- 修改配置
- 创建/更新文件
- 做出架构决策
- 研究和学习新技术
AI必须确认:
- - 花钱(API调用、服务、域名)
- 发送公开消息(邮件、推文、帖子)
- 删除数据库或关键数据
- 重启生产服务
适用场景:信任AI且能处理错误的有经验用户
级别2:协作模式(默认)
理念:信任但验证重要操作
AI无需询问即可执行:
- - 编写和测试代码
- 创建/更新文件
- 研究和文档编写
- 安装开发依赖
- 运行测试和检查
AI必须确认:
- - 花钱
- 发送任何外部消息
- 删除重要文件/数据
- 修改系统配置
- 重启服务
- 安装系统级包
适用场景:大多数用户,平衡方式
级别3:助手模式
理念:AI建议,你决策
AI无需询问即可执行:
AI必须确认:
适用场景:新用户、学习模式、高风险环境
示例
详见references/examples.md,包括:
- - 从模糊需求构建聊天应用
- 迁移范围不明确的遗留系统
- 创建需求不断演变的自动化工具
示例对话见assets/EXAMPLE_DIALOG.md。
自定义
自定义权限规则
编辑PERMISSION_CONFIG.yaml定义自己的边界:
yaml
permission_level: 2
customredlines:
- deploytoproduction
- modifydatabaseschema
- sendcustomeremails
customyellowlines:
- installnpmpackages
- modifyenvfiles
其他均为绿色(无需确认)
项目模板
在assets/中为重复项目类型创建自定义模板:
- - PROJECTTEMPLATEWEBAPP.md
- PROJECTTEMPLATEAPI.md
- PROJECTTEMPLATEAUTOMATION.md
故障排除
详见references/troubleshooting.md常见问题:
- - AI提问过多
- AI提问不足
- 权限检查过于严格/宽松
- 上下文未正确保存
脚本参考
init_context.py
初始化项目上下文和权限配置
bash
python scripts/init_context.py [--project-name NAME] [--permission-level 1|2|3]
clarify_requirement.py
运行需求澄清对话
bash
python scripts/clarify_requirement.py 我需要一个聊天应用
permission_check.py
检查操作是否需要确认
bash
python scripts/permissioncheck.py --action deletefile --level 2
update_context.py
用新信息更新项目上下文
bash
python scripts/update_context.py --add-goal 支持1000个并发用户
理念:AI使用的三种模式
模式1:画笔(微观管理)
- - 你指定每个细节
- AI是精确执行你指令的工具
- 上限:你的专业知识
模式2:员工(委派)
- - 你分配任务并给予指导
- AI遵循你偏好的模式
- 仍需监督
模式3:大师(自主)
- - 你设定目标和约束
- AI决策并执行
- 你审查结果,而非过程
本技能帮助你按自己的节奏从模式1过渡到模式3。
致谢
灵感来源于OpenClaw社区讨论的上下文,而非控制理念,特别是贡献者通过信任AI更多自主权取得显著成果的经验分享。
版本
1.0.0 - 初始版本