Sibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
Spec Workflow
Activation Contract
Use this first when
- The request is a new feature, multi-step product change, cross-module integration, or architecture/design task.
- Acceptance criteria are unclear and need to be made explicit before implementation.
- The work involves multiple files, user flows, database design, or UI design that needs staged confirmation.
Read before writing code if
- You are unsure whether the task should go straight to coding or should first go through requirements, design, and task planning.
- The request mentions a new page, a new system, a redesign, a workflow, or a multi-module refactor.
Then also read
- Frontend page or visual design work ->
../ui-design/SKILL.md
- Advanced data-model work ->
../postgresql-development-cloudbase/SKILL.md
Do NOT use for
- Small bug fixes with clear scope.
- One-file documentation updates.
- Straightforward config changes.
- Tiny refactors where the user already gave exact implementation instructions.
Common mistakes / gotchas
- Jumping into coding before acceptance criteria are explicit.
- Skipping user confirmation between requirements, design, and tasks.
- Writing vague tasks that do not map back to user-visible outcomes.
- Treating UI work as purely technical implementation without clarifying design intent.
Minimal checklist
- Decide whether the change really needs the full spec flow.
- If yes, stop and produce requirements first.
- If the change is small, low-risk, and acceptance is already clear, allow direct execution without forcing spec artifacts.
- Use EARS-style acceptance criteria.
- Get confirmation before moving to the next phase.
When to use this skill
Use this workflow for structured development when you need to:
- Define or refine a new feature
- Design complex architecture
- Coordinate changes across modules
- Plan database or UI-heavy work
- Improve requirement quality and acceptance boundaries
Decision rule
Use the full workflow when
- The task is medium or large
- The impact spans multiple modules
- Acceptance boundaries are fuzzy
- The user wants disciplined planning before implementation
Skip the full workflow when
- The task is small, low-risk, and already precise
- Goal, scope, and acceptance are already clear enough to execute directly
- The user explicitly wants a direct code change with no planning phase
Core workflow
Phase 1: Requirements
Create specs/<spec_name>/requirements.md.
What to do:
- Restate the problem and scope
- Write user stories
- Write acceptance criteria in EARS style
- Clarify business rules, constraints, and non-goals
EARS pattern:
While <optional precondition>, when <optional trigger>, the <system name> shall <system response>
Example:
When the user submits the form, the booking system shall validate required fields before creating the record.
Phase 2: Design
Create specs/<spec_name>/design.md.
What to do:
- Describe architecture and module boundaries
- Explain technology choices and trade-offs
- Define data model, API, security, and testing strategy as needed
- Use Mermaid only when a diagram materially improves clarity
Phase 3: Tasks
Create specs/<spec_name>/tasks.md.
What to do:
- Break the design into executable tasks
- Keep tasks specific and reviewable
- Link each task back to the relevant requirement
- Update task status as work progresses
Task format:
# Implementation Plan
- [ ] 1. Task title
- Specific work item
- Another concrete step
- _Requirement: 1
Phase 4: Execution
Only start implementation after the user confirms the task plan.
During execution:
- Keep task status current
- Finish one meaningful unit at a time
- Preserve traceability from change -> task -> requirement
Working rules for the agent
- Ask follow-up questions when the request is underspecified; do not guess core product behavior.
- Require confirmation between requirements, design, and task breakdown.
- Pull in
ui-design early when the change includes end-user pages or visual decisions.
- Keep documents concise but testable.
- Prefer user-visible outcomes over implementation-detail task names.
Output expectations
requirements.md -> problem, scope, user stories, EARS acceptance criteria
design.md -> architecture, technical approach, data/API/security/test notes
tasks.md -> actionable implementation checklist tied to requirements
1---2name: spec-workflow-33description: Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation, especially for multi-module work, unclear acceptance criteria, or architecture-heavy requests.4version: 2.37.65license: MIT6alwaysApply: false7metadata:8 source: https://skillmd.com/skills/tencentcloudbase/spec-workflow-39---1011## Sibling skills (local only)1213Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../auth-tool-cloudbase/SKILL.md`.1415If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.1617# Spec Workflow1819## Activation Contract2021### Use this first when2223- The request is a new feature, multi-step product change, cross-module integration, or architecture/design task.24- Acceptance criteria are unclear and need to be made explicit before implementation.25- The work involves multiple files, user flows, database design, or UI design that needs staged confirmation.2627### Read before writing code if2829- You are unsure whether the task should go straight to coding or should first go through requirements, design, and task planning.30- The request mentions a new page, a new system, a redesign, a workflow, or a multi-module refactor.3132### Then also read3334- Frontend page or visual design work -> `../ui-design/SKILL.md`35- Advanced data-model work -> `../postgresql-development-cloudbase/SKILL.md`3637### Do NOT use for3839- Small bug fixes with clear scope.40- One-file documentation updates.41- Straightforward config changes.42- Tiny refactors where the user already gave exact implementation instructions.4344### Common mistakes / gotchas4546- Jumping into coding before acceptance criteria are explicit.47- Skipping user confirmation between requirements, design, and tasks.48- Writing vague tasks that do not map back to user-visible outcomes.49- Treating UI work as purely technical implementation without clarifying design intent.5051### Minimal checklist5253- Decide whether the change really needs the full spec flow.54- If yes, stop and produce requirements first.55- If the change is small, low-risk, and acceptance is already clear, allow direct execution without forcing spec artifacts.56- Use EARS-style acceptance criteria.57- Get confirmation before moving to the next phase.5859## When to use this skill6061Use this workflow for structured development when you need to:6263- Define or refine a new feature64- Design complex architecture65- Coordinate changes across modules66- Plan database or UI-heavy work67- Improve requirement quality and acceptance boundaries6869## Decision rule7071### Use the full workflow when7273- The task is medium or large74- The impact spans multiple modules75- Acceptance boundaries are fuzzy76- The user wants disciplined planning before implementation7778### Skip the full workflow when7980- The task is small, low-risk, and already precise81- Goal, scope, and acceptance are already clear enough to execute directly82- The user explicitly wants a direct code change with no planning phase8384## Core workflow8586### Phase 1: Requirements8788Create `specs/<spec_name>/requirements.md`.8990What to do:9192- Restate the problem and scope93- Write user stories94- Write acceptance criteria in EARS style95- Clarify business rules, constraints, and non-goals9697EARS pattern:9899```text100While <optional precondition>, when <optional trigger>, the <system name> shall <system response>101```102103Example:104105```text106When the user submits the form, the booking system shall validate required fields before creating the record.107```108109### Phase 2: Design110111Create `specs/<spec_name>/design.md`.112113What to do:114115- Describe architecture and module boundaries116- Explain technology choices and trade-offs117- Define data model, API, security, and testing strategy as needed118- Use Mermaid only when a diagram materially improves clarity119120### Phase 3: Tasks121122Create `specs/<spec_name>/tasks.md`.123124What to do:125126- Break the design into executable tasks127- Keep tasks specific and reviewable128- Link each task back to the relevant requirement129- Update task status as work progresses130131Task format:132133```markdown134# Implementation Plan135136- [ ] 1. Task title137 - Specific work item138 - Another concrete step139 - _Requirement: 1140```141142### Phase 4: Execution143144Only start implementation after the user confirms the task plan.145146During execution:147148- Keep task status current149- Finish one meaningful unit at a time150- Preserve traceability from change -> task -> requirement151152## Working rules for the agent1531541. Ask follow-up questions when the request is underspecified; do not guess core product behavior.1552. Require confirmation between requirements, design, and task breakdown.1563. Pull in `ui-design` early when the change includes end-user pages or visual decisions.1574. Keep documents concise but testable.1585. Prefer user-visible outcomes over implementation-detail task names.159160## Output expectations161162- `requirements.md` -> problem, scope, user stories, EARS acceptance criteria163- `design.md` -> architecture, technical approach, data/API/security/test notes164- `tasks.md` -> actionable implementation checklist tied to requirements