Skip to content
Back to skills

Planning Workflows

ASecurity

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

  • 1,130 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 28, 2026
ai-agents

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned May 28, 2026

npx -y skills add TencentCloudBase/CloudBase-MCP --skill planning-workflows --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Planning Workflows?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Planning Workflows
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tencentcloudbase-planning-workflows/badge)](https://www.skillsdirectory.com/skills/tencentcloudbase-planning-workflows)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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`.

Files in this skill

  • SKILL.md1.1 KB
  • references/command-catalog.md401 B
  • references/source-commands.md4.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.