Hoang604
32 verified skills
archive
Archive completed task/spec work to ./.gtd/archive/
tools
codebase-overview
Analyze codebase architecture. Creates ./.gtd/CODEBASE.md
development
d-archive
Archive completed debug work to ./.gtd/archive/
development
d-inspect
Inspect code and propose root cause hypotheses. Creates ./.gtd/debug/current/HYPOTHESES.md
development
d-symptom
Clarify and document bug symptoms. Creates ./.gtd/debug/current/SYMPTOM.md
development
d-verify
Verify hypotheses with debug logging. Updates ./.gtd/debug/current/ROOT_CAUSE.md
development
codebase-overview
Analyze codebase architecture. Creates ./.gtd/CODEBASE.md
development
roadmap
Create sequential phases from spec. Creates ./.gtd/<task_name>/ROADMAP.md. User manually trigger, do not auto invoke this.
tools
write-test
manual trigger by user, do not auto invoke
testing
spec
Define what you want to build. Creates ./.gtd/<task_name>/SPEC.md. User manually trigger, do not auto invoke this.
development
archive
Archive completed task/spec work to ./.gtd/archive/. User manually trigger, do not auto invoke this.
tools
commit-spec
Create comprehensive commit message from spec phases and commit all changes
tools
d-execute
Execute bug fix plan. Creates ./.gtd/debug/current/FIX_SUMMARY.md
development
discuss-plan
(Optional) Discuss and refine a phase plan before execution
tools
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
testing
d-plan-fix
Create execution plan to fix root cause. Creates ./.gtd/debug/current/FIX_PLAN.md
development
plan-phase
Create execution plan for a phase. Creates ./.gtd/<task_name>/{phase}/PLAN.md. User manually trigger, do not auto invoke this.
tools
research
Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.
development
roadmap
Create sequential phases from spec. Creates ./.gtd/<task_name>/ROADMAP.md
tools
verify-spec
Verify that "Must Have" requirements from SPEC.md are implemented in the codebase.
development
verify-spec
Verify that "Must Have" requirements from SPEC.md are implemented in the codebase. User manually trigger, do not auto invoke this.
development
bootstrap
Initialize project backlog from architecture docs. Creates ./.gtd/BACKLOG.md
documentation
execute
Execute a plan. Creates ./.gtd/<task_name>/{phase}/SUMMARY.md
tools
expand-backlog
Break a high-level backlog item into executable sub-items
tools
plan
Create execution plan for a phase. Creates ./.gtd/<task_name>/{phase}/PLAN.md
tools
s:archive
Archive completed task/spec work to ./.gtd/archive/
tools
s:spec
Create SPEC.md for the next backlog item. Creates ./.gtd/<task_name>/SPEC.md
tools
spec
Define what you want to build. Creates ./.gtd/<task_name>/SPEC.md
development
commit-spec
Create comprehensive commit message from spec phases and commit all changes. User manually trigger, do not auto invoke this.
tools
execute
Execute a plan. Creates ./.gtd/<task_name>/{phase}/SUMMARY.md. User manually trigger, do not auto invoke this.
tools
update-codebase
Update CODEBASE.md with working knowledge gained during task execution. User manually trigger, do not auto invoke this.
development
review-plan
manual trigger by user, do not auto invoke
tools