pocket-help

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pocket Help

Pocket 帮助

The map of the Pocket ecosystem. Read this first to understand the workflow, choose the right skill, and continue from the current stage without loading every

SKILL.md

Core principle: Orient cheaply, then load deep. This skill summarizes and routes; open an individual skill only when reaching the stage that uses it.

Pocket 生态系统的导航图。先阅读本文以了解工作流、选择合适的 skill，并从当前阶段继续推进，而无需加载每一个

SKILL.md

。

核心原则： 先以低成本方式定位，再按需深入加载。本 skill 负责总结和路由；只有进入使用某个 skill 的阶段时，才打开该 skill。

What Pocket Is

Pocket 是什么

Pocket is a set of skills for systematic development — from a vague idea to reviewed code. It breaks work into bounded stages with explicit gates: explore → specify → plan → structure → develop → close.

Each stage produces an artifact (pitch doc → spec → execution plan → task files → commits → review reports) that the next stage consumes.

Pocket 是一组用于系统化开发的 skill，覆盖从模糊想法到经过审查的代码的整个过程。它将工作划分为边界明确、设有显式关卡的各个阶段：探索 → 明确规格 → 规划 → 结构化 → 开发 → 收尾。

每个阶段都会产出一项成果（pitch doc → spec → 执行计划 → 任务文件 → commits → 审查报告），供下一阶段使用。

Skill Roles

Skill 角色

Role	Skills	Use for
Chained workflow	`pocket-pitching` · `pocket-grinding` · `pocket-planning` · `pocket-structuring` · `pocket-development` · `pocket-closing`	Features and non-trivial work that benefit from reviewed handoffs between stages.
Standalone workflow	`bug-hunting` · `hotfix` · `brand-design` · `structured-research` · `pocket-help` · `pocket-init` · `pocket-education`	Focused work, onboarding, or guidance that does not need the full pipeline.
Optional adapter	`pocket-enterprise`	Remote lifecycle synchronization, only when the user explicitly enables Enterprise.

The

pocket-*

prefix identifies Pocket-owned skills; it does not mean every one is a pipeline stage.

pocket-help

pocket-init

, and

pocket-education

are standalone helpers, while

pocket-enterprise

is an optional adapter.

角色	Skills	用途
链式工作流	`pocket-pitching` · `pocket-grinding` · `pocket-planning` · `pocket-structuring` · `pocket-development` · `pocket-closing`	适合功能开发及其他需要经审查的阶段交接的非简单工作。
独立工作流	`bug-hunting` · `hotfix` · `brand-design` · `structured-research` · `pocket-help` · `pocket-init` · `pocket-education`	适合无需完整流水线的聚焦工作、入门或指导。
可选适配器	`pocket-enterprise`	用于远程生命周期同步；仅在用户明确启用 Enterprise 时使用。

pocket-*

前缀表示由 Pocket 提供的 skill；这并不意味着每个 skill 都是流水线阶段。

pocket-help

、

pocket-init

和

pocket-education

是独立辅助 skill，而

pocket-enterprise

是可选适配器。

Router — Which Skill Right Now?

路由——现在该用哪个 skill？

Your situation	Skill	Kind
Rough idea, no clear problem yet — need to explore	`pocket-pitching`	chained
Clear problem — need a spec + acceptance criteria	`pocket-grinding`	chained
Approved spec — need a TDD execution plan	`pocket-planning`	chained
Execution plan ready — sequence/phase it	`pocket-structuring`	chained
Plan or phase file ready — execute task-by-task	`pocket-development`	chained
Phase-level pass complete — reconcile and close	`pocket-closing`	chained
A bug, a failure, or "audit this code"	`bug-hunting`	standalone
Small-to-medium change, full pipeline is overkill	`hotfix`	standalone
Design system / brand identity / UI tokens	`brand-design`	standalone
An assumption to validate before planning	`structured-research`	standalone
New to Pocket or unsure which skill fits	`pocket-help`	standalone
Existing repo needs a local project guide or learner calibration	`pocket-init`	standalone
Learner wants to do the task themselves, with guidance and review	`pocket-education`	standalone (education)
User explicitly enables remote lifecycle synchronization for a compatible Core install	`pocket-enterprise`	optional adapter

Routing rules of thumb:

Don't know if the problem is well-formed? →
```
pocket-pitching
```
.
Problem is clear but needs a real feature plan? →
```
pocket-grinding
```
.
It's a quick, well-understood change? →
```
hotfix
```
.
Something is broken? →
```
bug-hunting
```
.
Holding an unverified assumption? →
```
structured-research
```
.
Already have an approved spec? →
```
pocket-planning
```
.
Repo has Pocket Education on, or the user says "teach me / I want to do it myself"? →
```
pocket-education
```
(the human implements).
User explicitly asks to enable Enterprise lifecycle synchronization? →
```
pocket-enterprise
```
; never infer this from credentials or repo configuration.

你的情况	Skill	类型
只有粗略想法，尚未明确问题——需要探索	`pocket-pitching`	链式
问题已明确——需要 spec + 验收标准	`pocket-grinding`	链式
spec 已获批准——需要 TDD 执行计划	`pocket-planning`	链式
执行计划已就绪——进行任务排序和分阶段	`pocket-structuring`	链式
计划或阶段文件已就绪——逐项执行任务	`pocket-development`	链式
阶段级检查已完成——核对结论并收尾	`pocket-closing`	链式
遇到 bug、失败，或需要审查代码	`bug-hunting`	独立
小到中等规模的变更，使用完整流水线过于繁重	`hotfix`	独立
设计系统 / 品牌标识 / UI tokens	`brand-design`	独立
规划前需要验证某个假设	`structured-research`	独立
初次使用 Pocket，或不确定哪个 skill 合适	`pocket-help`	独立
现有 repo 需要本地项目指南或学习者水平校准	`pocket-init`	独立
学习者希望亲自完成任务，同时获得指导和审查	`pocket-education`	独立（教育）
用户明确为兼容的 Core 安装启用远程生命周期同步	`pocket-enterprise`	可选适配器

路由经验法则：

不知道问题是否定义清楚？→
```
pocket-pitching
```
。
问题已明确，但需要完整的功能计划？→
```
pocket-grinding
```
。
这是快速且已充分理解的变更？→
```
hotfix
```
。
有什么东西坏了？→
```
bug-hunting
```
。
持有一个尚未验证的假设？→
```
structured-research
```
。
已经有获批的 spec？→
```
pocket-planning
```
。
Repo 已启用 Pocket Education，或者用户说 "teach me / I want to do it myself"？→
```
pocket-education
```
（由人实施）。
用户明确要求启用 Enterprise 生命周期同步？→
```
pocket-enterprise
```
；绝不要根据凭据或 repo 配置进行推断。

The End-to-End Flow

端到端流程

text

rough idea
   │  pocket-pitching     explore → pitch doc             [user chooses next]
   ▼
clear problem
   │  pocket-grinding     BDD discovery → approved spec   [hands off to planning]
   ▼
approved spec
   │  pocket-planning     TDD plan → full task packets    [routes to structuring]
   ▼
execution plan
   │  pocket-structuring  index + task files              [development handoff]
   ▼
plan / phase file
   │  pocket-development  task execution + in-loop audits [phase-level pass]
   ▼
reviewed phase
   │  pocket-closing      verdict reconciliation + close  [when closeout is authorized]

Handoff facts that matter:

```
pocket-grinding
```
hands an approved spec to
```
pocket-planning
```
.
```
pocket-planning
```
validates the plan and routes all plans to
```
pocket-structuring
```
.
```
pocket-structuring
```
creates an execution index and per-task files. It hands off to
```
pocket-development
```
when the user's existing instruction authorizes execution; otherwise it asks once for the missing authorization.
```
pocket-development
```
executes tasks, records per-task verdicts, runs a phase-level pass, and writes a durable phase handoff. It leaves the phase in
```
REVIEW
```
; if the user's request already authorizes end-to-end closeout, continue to
```
pocket-closing
```
, otherwise name it as the next step.
```
pocket-closing
```
reconciles verdicts and advances a reviewed phase; it appends that phase's section to
```
closeout.md
```
and does not review implementation code. It appends the final plan section after all phases close.
```
pocket-pitching
```
does not auto-chain — the user chooses whether to start
```
pocket-grinding
```
.

For the full stage-by-stage walkthrough, load

references/end-to-end-flow.md

. For concise inputs, outputs, and routing notes, load

references/skill-map.md

text

rough idea
   │  pocket-pitching     explore → pitch doc             [user chooses next]
   ▼
clear problem
   │  pocket-grinding     BDD discovery → approved spec   [hands off to planning]
   ▼
approved spec
   │  pocket-planning     TDD plan → full task packets    [routes to structuring]
   ▼
execution plan
   │  pocket-structuring  index + task files              [development handoff]
   ▼
plan / phase file
   │  pocket-development  task execution + in-loop audits [phase-level pass]
   ▼
reviewed phase
   │  pocket-closing      verdict reconciliation + close  [when closeout is authorized]

重要的交接事实：

```
pocket-grinding
```
将获批的 spec 交给
```
pocket-planning
```
。
```
pocket-planning
```
验证计划，并将所有计划路由到
```
pocket-structuring
```
。
```
pocket-structuring
```
创建执行索引和逐任务文件。当用户现有指令已授权执行时，它会移交给
```
pocket-development
```
；否则，它会针对缺失的授权询问一次。
```
pocket-development
```
执行任务、记录每项任务的审查结论、运行阶段级检查，并写入持久化的阶段交接记录。它会将阶段留在
```
REVIEW
```
状态；如果用户请求已授权端到端收尾，则继续进入
```
pocket-closing
```
，否则将后者列为下一步。
```
pocket-closing
```
核对各项结论并推进已审查的阶段；它会将该阶段的章节追加到
```
closeout.md
```
，但不会审查实现代码。所有阶段关闭后，它会追加计划的最终章节。
```
pocket-pitching
```
不会自动串联——由用户决定是否开始
```
pocket-grinding
```
。

如需完整的逐阶段操作说明，请加载

references/end-to-end-flow.md

。如需简要查看输入、输出和路由说明，请加载

references/skill-map.md

。

Pocket Education (opt-in mentor mode)

Pocket Education（可选导师模式）

With Pocket Education enabled (

/pocketto:pocket-init

Education Gate), the human writes the code and the agent teaches, reviews, and guides with progressive hints (

pocket-education

). The skill-specific learner profile (

foundation

guided

independent

per skill) lives in a

## Pocket Education

block in

AGENTS.md

CLAUDE.md

and is reused across sessions. It can gain a skill dimension when a task needs one; recalibration and persistent level changes remain learner-controlled.

In an Education repo, implementation skills check whether the learner wants guidance or a handoff. An explicit handoff already given in
```
pocket-education
```
authorizes that task; do not ask for the same confirmation again.
Education is local and independent of optional adapters. Without the block, nothing changes and no
```
edu
```
call is made.

启用 Pocket Education（

/pocketto:pocket-init

Education Gate）后，由人编写代码，agent 负责教学、审查和引导，并提供渐进式提示（

pocket-education

）。每个 skill 的学习者档案（对应

foundation

guided

independent

）位于

AGENTS.md

CLAUDE.md

中的

## Pocket Education

区块内，并跨会话复用。当任务需要时，该档案可以增加一个 skill 维度；重新校准和持久化的等级变更仍由学习者控制。

在 Education repo 中，实施类 skills 会检查学习者希望获得指导还是进行交接。
```
pocket-education
```
中已经明确给出的交接即视为已授权该任务；不要再次询问相同确认。
Education 是本地的，且独立于可选适配器。如果没有该区块，一切保持不变，也不会发起
```
edu
```
调用。

Optional Enterprise Adapter

可选 Enterprise 适配器

Use

pocket-enterprise

only after the user explicitly enables remote lifecycle synchronization for a compatible Core installation. Core remains local-first without it; do not infer consent from credentials or an existing registration.

仅当用户明确为兼容的 Core 安装启用远程生命周期同步后，才使用

pocket-enterprise

。没有该适配器时，Core 仍保持 local-first；不要根据凭据或已有注册记录推断用户同意。

When Pocket Beats a Lighter Flow

何时应使用 Pocket 而非轻量流程

Use the full pipeline when work has high ambiguity, spans many steps, needs BDD/TDD discipline, or requires phase gates and auditable handoffs.

For smaller work, choose a focused skill:

known bug or failure →
```
bug-hunting
```
small-to-medium change →
```
hotfix
```
design system or UI tokens →
```
brand-design
```
an assumption to validate →
```
structured-research
```

For the full comparison, load

references/pocket-vs-superpowers.md

当工作歧义度高、涉及多个步骤、需要 BDD/TDD 规范，或要求设置阶段关卡与可审计交接时，使用完整流水线。

对于规模较小的工作，选择聚焦的 skill：

明确的 bug 或故障 →
```
bug-hunting
```
小到中等规模的变更 →
```
hotfix
```
设计系统或 UI tokens →
```
brand-design
```
需要验证的假设 →
```
structured-research
```

如需完整对比，请加载

references/pocket-vs-superpowers.md

。

Context Budget Guidance

上下文预算指南

Start here to orient and route.
Load one skill for the current stage.
Load that skill's references only when its instructions call for them.

从这里开始定位和路由。
为当前阶段加载一个 skill。
仅当该 skill 的指令明确要求时，才加载它的参考文件。