workflow
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseWorkflow
工作流
High-velocity solo development. Idea to production same-day.
高速独立开发,从想法到上线可在当日完成。
Agent Capabilities
Agent 能力
| Capability | Used For | Required | Fallback |
|---|---|---|---|
| File read/write | Specs, config, history | Yes | — |
| Code search (grep/glob) | Discovery, context | Yes | — |
| Shell/command execution | Quality gates (lint, build, test) | Yes | List commands for user to run |
| Task/todo tracking | Phase management | Recommended | Track in spec Progress section |
| User interaction | Stuck escalation, risk flags | Recommended | Log decisions in spec Notes |
| Web/doc search | Pattern lookup | No | Use embedded patterns |
Fallback rule: If your agent lacks a capability, use the fallback. Never skip the workflow step — adapt the method.
| 能力 | 用途 | 是否必需 | 备选方案 |
|---|---|---|---|
| 文件读写 | 规格说明、配置、历史记录 | 是 | — |
| 代码搜索(grep/glob) | 发现、上下文获取 | 是 | — |
| Shell/命令执行 | 质量门禁(lint、构建、测试) | 是 | 列出命令供用户运行 |
| 任务/待办事项跟踪 | 阶段管理 | 推荐 | 在规格说明的进度部分跟踪 |
| 用户交互 | 问题升级、风险标记 | 推荐 | 在规格说明的备注部分记录决策 |
| 网页/文档搜索 | 模式查找 | 否 | 使用内置模式 |
备选规则:如果你的Agent不具备某项能力,请使用备选方案。绝不要跳过工作流步骤——要调整方法适配。
Commands
命令
| Command | Action | Reference |
|---|---|---|
| Create spec | plan.md |
| Time-boxed exploration | spike.md |
| Implement + validate | ship.md |
| Multi-perspective code review | review.md |
| Adversarial spec analysis | spec-review.md |
| Priority analysis + task proposals | focus.md |
| Validate + retro + archive | done.md |
| Abandon, preserve learnings | drop.md |
| Show state + suggest next | Status (below) |
No flags needed. The agent auto-detects intent from context:
- "review the spec" → manual review pause
- "skip tests" → skip test gate (documented)
- "emergency fix" → bypass spec ceremony
- "production ready" → production validation
| 命令 | 操作 | 参考文档 |
|---|---|---|
| 创建规格说明 | plan.md |
| 限时探索 | spike.md |
| 实现 + 验证 | ship.md |
| 多视角代码评审 | review.md |
| 对抗性规格说明分析 | spec-review.md |
| 优先级分析 + 任务建议 | focus.md |
| 验证 + 回顾 + 归档 | done.md |
| 放弃,保留经验 | drop.md |
| 显示状态 + 建议下一步 | 状态(如下) |
无需标记,Agent会从上下文中自动检测意图:
- "review the spec" → 手动评审暂停
- "skip tests" → 跳过测试门禁(已记录)
- "emergency fix" → 绕过规格说明流程
- "production ready" → 生产环境验证
Flow
流程
focus → plan {idea} → ship → [implement/review/fix loop] → doneQuick mode (<2h):
Don't know what to work on:
ship {idea} → donefocusfocus → plan {idea} → ship → [实现/评审/修复循环] → done快速模式(<2小时):
不知道该做什么:
ship {idea} → donefocusPhilosophy
理念
- Spec-first: All work needs a spec (creates one if missing)
- Ship loop: Build → review → fix until clean
- Quality gates: lint → typecheck → build → test (auto-detected per project)
- Human controls deployment: Agent codes, you push/deploy
- Done same-day: Scope to what ships today
- Own planning: Never use the host agent's built-in plan mode (EnterPlanMode, etc.). This skill writes real spec files to .
specs/active/
- 规格优先:所有工作都需要规格说明(如果缺失则自动创建)
- 上线循环:构建 → 评审 → 修复直到无问题
- 质量门禁:lint → 类型检查 → 构建 → 测试(根据项目自动检测)
- 人工控制部署:Agent编写代码,由你推送/部署
- 当日完成:限定在当日可上线的范围
- 自主规划:绝不要使用宿主Agent的内置规划模式(如EnterPlanMode等)。本技能会将真实的规格说明文件写入。
specs/active/
Spec Tiers
规格说明层级
| Tier | Size | Spec | Task Tracking |
|---|---|---|---|
| trivial | <5 LOC | None — just do it | No |
| micro | <30 LOC | Inline comment in code | No |
| mini | <100 LOC | Spec file, minimal | Yes (if available) |
| standard | 100+ LOC | Full spec with checklist | Yes (if available) |
| 层级 | 规模 | 规格说明 | 任务跟踪 |
|---|---|---|---|
| trivial | <5 行代码 | 无——直接执行 | 否 |
| micro | <30 行代码 | 代码中的内联注释 | 否 |
| mini | <100 行代码 | 规格说明文件,极简 | 是(如果可用) |
| standard | 100+ 行代码 | 带检查清单的完整规格说明 | 是(如果可用) |
Action Router
操作路由
User input
│
├─ "plan", "spec", "design" → Load references/actions/plan.md
├─ "spike", "explore", "investigate" → Load references/actions/spike.md
├─ "ship", "implement", "fix", "build" → Load references/actions/ship.md
├─ "review", "check code" → Load references/actions/review.md
├─ "review spec", "analyze spec",
│ "challenge spec" → Load references/actions/spec-review.md
├─ "focus", "what should i do",
│ "prioritize", "overwhelmed" → Load references/actions/focus.md
├─ "done", "finish", "complete" → Load references/actions/done.md
├─ "drop", "abandon" → Load references/actions/drop.md
└─ "workflow", "what's next", "what now",
"what's up", "whats up", "status" → Status Action (below)Loading rule: Read the action file BEFORE executing. The action file contains all logic, task templates, and references needed.
用户输入
│
├─ "plan", "spec", "design" → 加载 references/actions/plan.md
├─ "spike", "explore", "investigate" → 加载 references/actions/spike.md
├─ "ship", "implement", "fix", "build" → 加载 references/actions/ship.md
├─ "review", "check code" → 加载 references/actions/review.md
├─ "review spec", "analyze spec",
│ "challenge spec" → 加载 references/actions/spec-review.md
├─ "focus", "what should i do",
│ "prioritize", "overwhelmed" → 加载 references/actions/focus.md
├─ "done", "finish", "complete" → 加载 references/actions/done.md
├─ "drop", "abandon" → 加载 references/actions/drop.md
└─ "workflow", "what's next", "what now",
"what's up", "whats up", "status" → 状态操作(如下)加载规则:执行前先读取操作文件。操作文件包含所需的所有逻辑、任务模板和参考资料。
Status Action
状态操作
No separate action file — logic is inline here. Detect current state, suggest next action:
1. Check specs/active/ for active spec
2. Check git status for uncommitted work
3. Check task list for in-progress items
State → Suggestion:
No spec, no changes → "Ready. Run: plan {idea}"
Active spec, no code → "Spec ready. Run: ship"
Active spec, code WIP → "In progress. Run: ship (resumes)"
Active spec, code done → "Ready to close. Run: done"
No spec, dirty tree → "Uncommitted work. Run: ship (creates spec) or done"Output: Follow status-output.md.
无单独的操作文件——逻辑内联在此处。检测当前状态,建议下一步操作:
1. 检查 specs/active/ 中的活跃规格说明
2. 检查 git 状态是否有未提交的工作
3. 检查任务列表中的进行中项
状态 → 建议:
无规格说明,无变更 → "准备就绪。运行:plan {idea}"
有活跃规格说明,无代码 → "规格说明已准备好。运行:ship"
有活跃规格说明,代码开发中 → "进行中。运行:ship(恢复)"
有活跃规格说明,代码已完成 → "准备收尾。运行:done"
无规格说明,工作区有变更 → "存在未提交工作。运行:ship(创建规格说明)或 done"输出:遵循 status-output.md。
Project Structure
项目结构
specs/
active/ ← Current work (0-1 specs)
backlog/ ← Queued work from focus
shipped/ ← Completed features
dropped/ ← Abandoned with learnings
history.log ← One-line per feature shipped/droppedspecs/
active/ ← 当前工作(0-1 个规格说明)
backlog/ ← 来自 focus 的待处理工作
shipped/ ← 已完成的功能
dropped/ ← 已放弃但保留经验的工作
history.log ← 每个已上线/已放弃功能的单行记录Configuration
配置
All behavior is configurable by editing the skill files directly.
| What to change | Edit |
|---|---|
| Action logic, gates, limits | |
| Output format | |
| Spec structure | |
| Quality gate commands/levels | |
| Session resume, stuck detection | |
所有行为可通过直接编辑技能文件进行配置。
| 要修改的内容 | 编辑文件 |
|---|---|
| 操作逻辑、门禁、限制 | |
| 输出格式 | |
| 规格说明结构 | |
| 质量门禁命令/级别 | |
| 会话恢复、停滞检测 | |
References
参考资料
Actions:
- Plan | Ship | Review | Spec Review | Focus | Done | Drop | Spike
Output templates:
- Plan + Spec Review | Ship | Review | Focus | Done | Drop | Spike | Status
Review standards:
- Production Standards
Specs & gates:
- Spec template | Quality gates | Session management | Memory update | Testing automation
Patterns:
- Implementation | Planning | Debugging | Decisions | Decomposition | Regression testing
操作:
- Plan | Ship | Review | Spec Review | Focus | Done | Drop | Spike
输出模板:
- Plan + Spec Review | Ship | Review | Focus | Done | Drop | Spike | Status
评审标准:
- Production Standards
规格说明与门禁:
- Spec template | Quality gates | Session management | Memory update | Testing automation
模式:
- Implementation | Planning | Debugging | Decisions | Decomposition | Regression testing