---
name: Planning Workflows
slug: planning-workflows
category: AI Engineering
description: Planning Workflows standardizes how to choose between spec and no-spec execution using local slash commands. Use it for new or risky work that needs requirements, design, and tasks, or for small scoped fixes that can proceed directly.
github: "https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/planning-workflows"
language: TypeScript
stars: 1074
forks: 134
install: "npx degit https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/planning-workflows ~/.claude/skills/planning-workflows"
installs_to: ~/.claude/skills/planning-workflows
source_path: skills/planning-workflows/SKILL.md
collection_size: 25
category_size: 2451
collection_url: "https://dirskills.com/collections/TencentCloudBase/CloudBase-AI-Toolkit"
added: 2026-08-21T05:13:33.383Z
last_synced: 2026-08-21T05:13:33.383Z
canonical_url: "https://dirskills.com/skills/planning-workflows"
---

# Planning Workflows

Planning Workflows standardizes how to choose between spec and no-spec execution using local slash commands. Use it for new or risky work that needs requirements, design, and tasks, or for small scoped fixes that can proceed directly.

**Install:**

```bash
npx degit https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/planning-workflows ~/.claude/skills/planning-workflows
```

## README

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