mcpbeat

Planning Workflows

tencentcloudbase/planning-workflows

Spec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).

1k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1066
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill planning-workflows

The instruction itself

6 sections, as written by the author

Planning Workflows (spec / no-spec)

This skill standardizes how to choose and execute planning modes using local slash commands.

When to use this skill

Use this skill when the user:

  • wants a full spec workflow before implementation
  • wants to skip spec and execute directly for small scoped tasks
  • asks how to decide between spec vs no-spec

Source of truth

  • references/source-commands.md

Decision rules

  • Prefer spec when work is new/complex, cross-module, risky, or acceptance criteria are unclear.
  • Prefer no-spec when work is small, low-risk, well-scoped (docs/config/simple fixes).

Execution rules

  • Read the matching command template from references/source-commands.md.
  • Follow it as a phase gate workflow:
  • do not skip required confirmations when running spec mode
  • keep scope tight when running no-spec mode
  • Keep artifacts in the repo conventions (e.g. specs/<name>/...) when spec is selected.

Command mapping

See references/command-catalog.md.

How to use it

Copy the folder

Take tencentcloudbase/planning-workflows from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.