planning-workflows
Spec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill planning-workflows --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. Read the matching command template from `references/source-commands.md`. 2. Follow it as a phase gate workflow: - do not skip required confirmations when running spec mode - keep scope tight when running no-spec mode 3. Keep artifacts in the repo conventions (e.g. `specs/<name>/...`) when spec is selected. ## Command mapping See `references/command-catalog.md`.
- When to use this skill
- Source of truth
- Decision rules
- Execution rules
- Command mapping
What does the planning-workflows skill do?
Spec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).
How do I install it?
Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill planning-workflows --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From TencentCloudBase/CloudBase-AI-Toolkit, a repository with 1,066 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.