Skip to content
Development
Skill

/planning-workflows

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

From plugin
cloudbase-ai-toolkit
1.1k98 skills3 agents7 commands2 MCP
Install
$ npx -y skills add TencentCloudBase/CloudBase-AI-Toolkit --skill planning-workflows --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/planning-workflows

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

planning-workflows.SKILL.md
name: planning-workflows
description: Spec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).

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`.

Ships withcloudbase-ai-toolkit

AI writes the code. CloudBase runs the backend. The CloudBase integration layer for AI coding tools: Plugin installs the stack, Skills steer how code is written, MCP operates databases, functions, storage, and deploys from chat.

Get the whole plugin

Other skills on cloudbase-ai-toolkit.