plugins/gwt/skills/gwt-spec-analyze/SKILL.md
Analyze a `gwt-spec` artifact set for completeness and consistency across `spec.md`, `plan.md`, `tasks.md`, and supporting artifacts. Detect missing traceability, unresolved clarifications, and constitution gaps before implementation, and distinguish auto-fixable gaps from true decision blockers.
npx skillsauth add akiojin/gwt gwt-spec-analyzeInstall 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.
Use this skill as the final gate before implementation starts.
gwt-spec-analyze is still non-implementation work.gwt-spec-ops can repair automatically and gaps that truly require user input.doc:spec.mddoc:plan.mddoc:tasks.mdmemory/constitution.mdOptional but validated when present:
doc:research.mddoc:data-model.mddoc:quickstart.mdcontract:*Clarification completeness
[NEEDS CLARIFICATION] markers remainSpec completeness
Plan completeness
Constitution Check existsTechnical Context and Phased Implementation are concreteTask traceability
Constitution alignment
Complexity Tracking## Analysis Report: #<number>
Status: CLEAR | AUTO-FIXABLE | NEEDS-DECISION
Blocking items:
- A1. <artifact gap>
- A2. <traceability gap>
Next:
- `gwt-spec-ops`
- `gwt-spec-implement`
- ask user for decision
CLEAR: implementation may proceed through gwt-spec-implementAUTO-FIXABLE: gwt-spec-ops should repair the artifact set and rerun analysisNEEDS-DECISION: the report must point to the exact user decision or unresolved ambiguitypython3 "${CLAUDE_PLUGIN_ROOT}/skills/gwt-spec-ops/scripts/spec_artifact.py" \
--repo "." \
--issue "<number>" \
--list
tools
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'
testing
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.
testing
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'.
business
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.