akiojin/gwt-spec-tasks
plugins/gwt/skills/gwt-spec-tasks/SKILL.md
Generate `tasks.md` for an existing `gwt-spec` from `spec.md` and `plan.md`, grouped by phase and user story with exact file paths, `[P]` parallel markers, and test-first ordering. Use directly or through `gwt-spec-ops`.
$ install --global
skillsauthnpx skillsauth add akiojin/gwt gwt-spec-tasksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 2, 2026, 3:55 PM55.9s1 file scanned
SKILL.md
- name:
- gwt-spec-tasks
- description:
- Generate `tasks.md` for an existing `gwt-spec` from `spec.md` and `plan.md`, grouped by phase and user story with exact file paths, `[P]` parallel markers, and test-first ordering. Use directly or through `gwt-spec-ops`.
gwt SPEC Tasks
Use this skill to turn the approved spec and plan artifacts into executable work items.
- If
plan.mdis missing, usegwt-spec-planfirst. - If clarification blockers remain in
spec.md, usegwt-spec-clarifyfirst. - Do not invent scope that is not traceable to
spec.mdorplan.md. - When traceability gaps are mechanical and obvious, repair
tasks.mdinstead of stopping the workflow.
Required inputs
doc:spec.mddoc:plan.md- Optional:
doc:research.md,doc:data-model.md,doc:quickstart.md,contract:*
tasks.md structure
tasks.md must use this phase model:
- Setup
- Foundational
- User Story phases (
US1,US2, ...) - Polish / Cross-Cutting
Each task must include:
- Task ID
[P]when parallelizable- linked user story ID where applicable
- exact path or module
- concrete action
Workflow
-
Read the source artifacts.
- Extract user stories, acceptance scenarios, affected modules, and contracts.
-
Lay out phase order.
- Setup before shared infra
- Foundational before story-specific tasks
- Story phases before final polish
-
Generate test-first tasks.
- Add validation tasks before or alongside implementation tasks for each story.
- Include contract/integration/e2e coverage when the spec implies it.
-
Add exact implementation tasks.
- Use concrete file paths or modules.
- Mark
[P]only when the write scopes do not overlap.
-
Validate traceability.
- Every user story must have implementation and verification tasks.
- Every declared contract/data-model change must have at least one task.
-
Write
tasks.mdand continue into analysis.- Return the artifact to
gwt-spec-ops, or proceed directly togwt-spec-analyzewhen the flow is already active.
- Return the artifact to
Exit criteria
tasks.md is valid only when:
- every user story is covered
- no task is vague
- test tasks are present where acceptance scenarios require proof
- parallel markers are defensible
Operations
python3 "${CLAUDE_PLUGIN_ROOT}/skills/gwt-spec-ops/scripts/spec_artifact.py" \
--repo "." \
--issue "<number>" \
--upsert \
--artifact "doc:tasks.md" \
--body-file /tmp/tasks.md
Related Skills
akiojin/tui-design
tools
VerifiedTrustedCommunity
Create distinctive, production-grade terminal user interfaces. Use when building TUI components with ratatui, CLI output styling, or xterm.js terminal rendering. Triggers: 'design TUI', 'terminal UI', 'TUIデザイン', 'ターミナルUI', 'ratatui widget'
3SKILL.mdUpdated Apr 15, 2026
akiojin/gwt-spec-search
testing
VerifiedTrustedCommunity
Semantic search over SPEC Issues (GitHub Issue cache at ~/.gwt/cache/issues/) using vector embeddings. Use when searching for existing specs, finding related specs, checking for duplicate specs, or determining which spec owns a scope. Mandatory preflight before gwt-discussion when the work may need a SPEC owner. Use when user says 'search specs', 'find related specs', 'check for duplicate specs', or asks which spec owns a scope.
3SKILL.mdUpdated Apr 15, 2026
akiojin/gwt-search
testing
VerifiedTrustedCommunity
Mandatory preflight before gwt-discussion, gwt-register-issue, and gwt-fix-issue. Use proactively before creating any SPEC or Issue owner or before reusing an existing one. Searches SPEC Issues, GitHub Issues, and project files via ChromaDB. Triggers: 'search', 'find related', 'check duplicates'.
3SKILL.mdUpdated Apr 15, 2026
akiojin/gwt-register-issue
business
VerifiedTrustedCommunity
Use when the user wants to register new work from a bug report, idea, or task description and an existing GitHub Issue number is not already known.
3SKILL.mdUpdated Apr 15, 2026