Planning Workflows Agent Skill
Spec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill planning-workflowsThe instruction itself
6 sections, as written by the authorPlanning 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.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take tencentcloudbase/planning-workflows from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.