Planning Workflows (spec / no-spec)
SkillMediaSpec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Planning Workflows (spec / no-spec) skill
What this skill tells your AI
The instructions your AI receives, as published by tencentcloudbase/cloudbase-ai-toolkit in skills/planning-workflows/SKILL.md and read by ahel’s review.
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.specs/is a local-only directory in this repo: nevergit addit (it is gitignored). Sync / retrieve it through the private archive described inAGENTS.mdsection<internal_dirs>.
Command mapping
See references/command-catalog.md.
Signals
- GitHub stars
- 1k
- Forks
- 138
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
planning-workflows- Source
- github.com/tencentcloudbase/cloudbase-ai-toolkit