Skip to content
Pocketto
Standalone skills

pocket-help

pocket-help maps the Pocket skills: what Pocket is, which skill fits the task in front of you, and how the local flow works, without loading every skill.

pocket-help is the map of the Pocket ecosystem: what Pocket is, which skill to use right now, and how the local development flow works, without loading every skill into context.

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

When to use it

  • You are new to Pocketto or unsure which skill fits.
  • You ask "what is pocket", "how do I use pocket", "which pocket skill".

When not to use it: you already know the stage you are in. Go straight to its skill.

Prerequisites

None. This is the recommended first command after installation.

How to invoke it

/pocketto:pocket-help

On Pi: "what is pocket", "how do I use pocket", or "pocket-help".

How it works

It reads your question, classifies your situation, and routes:

  • Chained workflow: the six pipeline stages, for features and non-trivial work with reviewed handoffs.
  • Standalone workflow: the everyday skills, bug-hunting, hotfix, brand-design, structured-research, pocket-help, pocket-init, pocket-education.
  • Optional adapter: pocket-enterprise, only when you explicitly enable remote lifecycle synchronization.

Its routing rules of thumb, verbatim:

  • 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
  • Repo has Education on, or you say "teach me"? → pocket-education (the human implements)
  • Explicitly enabling Enterprise? → pocket-enterprise (never inferred from credentials)

Outputs and artifacts

None: orientation and a route. It also explains the end-to-end flow, the handoff facts (what auto-chains and what waits for you), and when the full pipeline beats a lighter flow: high ambiguity, many steps, BDD/TDD discipline, or phase gates and auditable handoffs.

On this page