akiojin/gwt-spec-register
plugins/gwt/skills/gwt-spec-register/SKILL.md
Create a new GitHub Issue-first SPEC container when no existing canonical SPEC fits. Seed the Issue body as an artifact index plus a `spec.md` comment, then continue into SPEC orchestration unless the user explicitly asks for register-only behavior.
$ install --global
skillsauthnpx skillsauth add akiojin/gwt gwt-spec-registerInstall 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 PM56.8s1 file scanned
SKILL.md
- name:
- gwt-spec-register
- description:
- Create a new GitHub Issue-first SPEC container when no existing canonical SPEC fits. Seed the Issue body as an artifact index plus a `spec.md` comment, then continue into SPEC orchestration unless the user explicitly asks for register-only behavior.
gwt SPEC Register
Use this skill to create a new gwt-spec Issue container only after confirming that no
existing canonical SPEC should own the scope.
gwt-spec-register owns creation, then normally returns control to gwt-spec-ops.
- If the user wants to register new work and it is still unclear whether it should become a plain Issue or a SPEC, use
gwt-issue-registerfirst. - If an existing
gwt-specIssue already fits, usegwt-spec-opsinstead. - If the user starts from an existing plain Issue and the correct path is still unclear, use
gwt-issue-resolvefirst.
Mandatory preflight: search existing spec first
Before creating a new spec issue, use gwt-issue-search first.
Required behavior:
- Ensure
gh auth statusis valid before anyindex-issuescall - Update the Issues index if needed
- Run semantic Issue search with queries derived from the current request
- Prefer an existing canonical integrated SPEC over creating a new point SPEC
- Create a new
gwt-specIssue only when no suitable canonical SPEC exists
Do not create a new SPEC when an existing canonical SPEC clearly owns the scope.
SPEC ID and label
- SPEC ID = GitHub issue number
- Spec issues must carry the
gwt-speclabel
Required Issue body structure
New SPEC Issues must use this compact index structure:
<!-- GWT_SPEC_ID:#{number} -->
## Artifact Index
- `doc:spec.md`
- `doc:plan.md` (planned)
- `doc:tasks.md` (planned)
- `doc:research.md` (planned)
- `doc:data-model.md` (planned)
- `doc:quickstart.md` (planned)
- `contract:*`
- `checklist:*`
## Status
- Phase: Specify
- Clarification: Required
- Planning: Pending `gwt-spec-ops`
## Links
- Parent: ...
- Related: ...
- PRs: ...
Required initial spec.md artifact
After issue creation, create a doc:spec.md issue comment with this minimum structure:
<!-- GWT_SPEC_ARTIFACT:doc:spec.md -->
doc:spec.md
# Feature Specification: <title>
## Background
...
## User Stories
### User Story 1 - <title> (Priority: P1)
...
## Acceptance Scenarios
1. Given ...
## Edge Cases
- ...
## Functional Requirements
- FR-001 ...
## Non-Functional Requirements
- NFR-001 ...
## Success Criteria
- SC-001 ...
Workflow
-
Verify gh authentication.
- Run
gh auth statusin the repo. - If unauthenticated, stop and ask the user to log in.
- Run
-
Search for an existing canonical SPEC.
- Use
gwt-issue-searchwith at least 2 queries. - If a canonical SPEC exists, switch to
gwt-spec-opsand continue there.
- Use
-
Create the new
gwt-specIssue.- Use the built-in spec issue creation path when available.
- If the built-in path is unavailable, use the documented
gh issue createfallback. - If
gh issue create/gh issue edithits a secondary rate limit, use the REST issue endpoints (POST/PATCH /repos/<owner>/<repo>/issues/...) instead of stopping. - After creation, update
<!-- GWT_SPEC_ID:#NEW -->to<!-- GWT_SPEC_ID:#{number} -->.
-
Seed the initial
spec.mdartifact.- Fill the artifact with the minimum context from the originating Issue or request.
- Use
[NEEDS CLARIFICATION: ...]instead of guessing. - Do not create
plan.mdortasks.mdhere.
-
Continue through
gwt-spec-opsunless register-only was explicitly requested.- Pass the created issue number and source context into
gwt-spec-ops. gwt-spec-registershould not stop at the first handoff boundary when the user's request is to keep moving.
- Pass the created issue number and source context into
Operations (gh CLI fallback)
Artifact comments should be created with the shared helper:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/gwt-spec-ops/scripts/spec_artifact.py" \
--repo "." \
--issue "<number>" \
--upsert \
--artifact "doc:spec.md" \
--body-file /tmp/spec.md
The shared helper uses GitHub issue comment REST endpoints for create/update and should be preferred over raw gh issue comment.
Create new spec issue
gh issue create --label gwt-spec --title "feat: ..." --body "$(cat <<'EOF'
<!-- GWT_SPEC_ID:#NEW -->
## Artifact Index
- `doc:spec.md`
- `doc:plan.md` (planned)
- `doc:tasks.md` (planned)
- `doc:research.md` (planned)
- `doc:data-model.md` (planned)
- `doc:quickstart.md` (planned)
- `contract:*`
- `checklist:*`
## Status
- Phase: Specify
- Clarification: Required
- Planning: Pending `gwt-spec-ops`
## Links
- Parent: ...
- Related: ...
- PRs: ...
EOF
)"
Finalize marker after creation
gh issue edit {number} --body "$(updated body with <!-- GWT_SPEC_ID:#{number} -->)"
If gh issue create or gh issue edit is rate-limited, fall back to:
gh api "repos/<owner>/<repo>/issues" --method POST --input /tmp/spec-create.json
gh api "repos/<owner>/<repo>/issues/{number}" --method PATCH --input /tmp/spec-edit.json
Create initial spec.md artifact comment
cat <<'EOF' >/tmp/spec.md
<!-- GWT_SPEC_ARTIFACT:doc:spec.md -->
# Feature Specification: ...
## Background
...
## User Stories
### User Story 1 - ... (Priority: P1)
...
## Acceptance Scenarios
1. Given ...
## Edge Cases
- ...
## Functional Requirements
- FR-001 ...
## Non-Functional Requirements
- NFR-001 ...
## Success Criteria
- SC-001 ...
EOF
python3 "${CLAUDE_PLUGIN_ROOT}/skills/gwt-spec-ops/scripts/spec_artifact.py" \
--repo "." \
--issue "{number}" \
--upsert \
--artifact "doc:spec.md" \
--body-file /tmp/spec.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