.claude/skills/task/SKILL.md
Create a new task (bug or refactoring) with spec and progress tracking. Use when user wants to create a task or mentions /task command.
npx skillsauth add rakovi4/continue-example taskInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
bug or refactoringList ALL directories under ProductSpecification/tasks/ AND ProductSpecification/tasks/done/ (use ls). For EACH folder, extract the leading integer (e.g., 1-refactoring-task-entity -> 1, 2-bug-modal-scroll -> 2). List every extracted number explicitly, then pick the max. Next number = max + 1. If no folders exist, start at 1. All task types share one global sequence -- a bug after refactoring task 1 gets number 2, not 1. Done tasks still occupy their numbers.
Verification (mandatory): Before creating the folder, confirm that NO existing folder starts with the chosen number. Run ls ProductSpecification/tasks/ | grep "^{N}-" -- if it returns results, increment N and re-check.
If arguments provided, parse type (bug or refactoring) and title from args.
If no arguments, ask interactively: type and short title (2-5 words).
Create ProductSpecification/tasks/{N}-{type}-{slug}/ where slug is lowercase-hyphenated title.
Gather from user:
All types: Problem, Solution, Affected Layers (domain, usecase, h2, rest, email, frontend), Key Files.
Bug only: Reproduction steps.
Refactoring only: Numbered steps with clear scope.
Write ProductSpecification/tasks/{N}-{type}-{slug}/spec.md using the format in .claude/templates/task/creation-formats.md.
Select fix profile based on type and affected layers:
| Affected Layers | Section |
|-----------------|---------|
| Backend only | ## Backend (standard backend sequence with [ ] adapters-discovery) |
| Frontend only | ## Frontend (standard frontend sequence) |
| Both | ## Backend + ## Frontend |
| Refactoring | ## Fix with user-defined steps |
Write ProductSpecification/tasks/{N}-{type}-{slug}/progress.md using the matching format from the template. Bug tasks use [ ] adapters-discovery -- adapter discovery runs when this step is reached. Refactoring steps are user-defined from step 4.
Show spec.md and progress.md to user for review. Commit both files.
task: spec (Task {N}, {title}).claude/templates/task/creation-formats.md -- spec.md format, progress.md formatstesting
Run use-case module tests quickly. Use when user wants to run use-case tests or mentions /test-usecase command.
development
Generate BDD test specifications for story in 6 categories (API, UI, Load, Infrastructure, Security, Integration). Use when user wants to create test cases or mentions /test-spec command.
testing
Review tests to replace loose validation (contains, isNotNull, isNotEmpty) with strict validation (isEqualTo on parsed fields). Use when user wants to improve test assertions or mentions /test-review command.
development
Run frontend tests. Use when user wants to run frontend unit tests or mentions /test-frontend command.