plan-reviewer
Review implementation plans (plan.md) for spec compliance and feasibility.
task-management
Framework for systematic task execution using a state machine (Planning, Execution, Closing). Used for (1) complex feature implementation requiring multiple steps, (2) root-cause analysis and bug fixing, and (3) creation and organization of comprehensive design documents.
github-review-cycle
manage pull request code reviews, approvals, comments, and feedback cycles
vulnerability-management
Vulnerability assessment, tracking, and remediation management. Process scan results, prioritize findings, and track remediation progress. Use for vulnerability management programs and security assessments.
star-techspec
Do techspec step of the PLANNING phase of star-team workflow.
merge-archive-plan
Archive completed implementation plans after PR merge. Use when a plan's implementation has been merged to main, or after plan-execute completes on main branch.
spec-driven-dev
ไปๆง้งๅ้็บในใญใซใใขใคใใขใใไปๆงๆธไฝๆใ่ชๅพ้็บใซใผใใๆค่จผใพใงไธ้ฃใฎๆตใใใตใใผใใๆฐ่ฆใใญใธใงใฏใ้ๅงๆใซไฝฟ็จใ
project-review
This skill should be used for reviewing current project against mature project patterns, tool capabilities, and org standards. Triggers include "review this project", "what am I missing", "align with standards", "check tool usage", "compare to arbor/koto", or proactively at session start in unfamiliar projects. Surfaces gaps in patterns, underutilized tools, and org standard deviations.
workflowresolve-escalation
Records a resolution for a human escalation.
issue-splitter
Split complex issues into smaller, implementable sub-issues. Called automatically when ComplexityGate determines an issue needs splitting.
create-issue
Creates GitHub issues with proper formatting and labels. Use when the user wants to report a bug, request a feature, or create documentation tasks.
do-workflow-project
๋ฌธ์ ์์ฑ, ์ธ์ด ์ด๊ธฐํ, ํ ํ๋ฆฟ ์ต์ ํ๋ฅผ ํตํฉํ ํ๋ก์ ํธ ๊ด๋ฆฌ ์์คํ
close-work-cycle
HAIOS Close Work Cycle for structured work item closure. Use when closing work items. Guides VALIDATE->ARCHIVE->MEMORY workflow with DoD enforcement.
aico-pm-story-acceptance
Verify and close stories after frontend/backend tasks are completed. Check ALL related task files, update story acceptance criteria checkboxes. UNIQUE VALUE: Ensures BOTH frontend AND backend tasks are verified before closing story. Prevents premature story closure. Use this skill when: - Frontend or backend notifies "task completed, please verify" - User asks to "verify story", "accept story", "close story", "mark story done" - Need to check if a story can be marked as complete - User asks "is story X done?", "can we close story X?" CRITICAL: Must check BOTH frontend tasks (docs/reference/frontend/tasks/) AND backend tasks (docs/reference/backend/tasks/) before closing. Output: Update story file checkboxes from `- [ ]` to `- [x]`
nfr-promote-ready
BacklogใฎIdeaใใๅฎ่ฃ ็ๆๅฏ่ฝใชNFR๏ผReady๏ผใจใใฆ docs/nfr/NNN_topic/nfr.md ใซๆๆ ผใใdocs/nfr/INDEX.md ใๆดๆฐใใใๅฎ่ฃ ใฏ่กใใใใใญใฅใกใณใไฝๆใจ็ดขๅผๆดๆฐใฎใฟใ่กใใUse when the user wants to promote a backlog NFR idea to Ready status for implementation.
diagram-maker
Create state machine diagrams of existing components to map out all code paths and verify system understanding. Use when analyzing user flows, authentication, multi-step processes, or any stateful logic to ensure comprehensive coverage of all transitions, edge cases, and error paths.
workflow-phase-convention
ๅ จใฏใผใฏใใญใผใงไธ่ฒซใใPhase็ชๅทไฝ็ณปใๆฟ่ชใฒใผใ่ฆ็ดใๆๅคงใชใใฉใคๅๆฐใฎๆจๆบใๅฎ็พฉ
self-checker
์์ ์๋ฃ ํ ์๊ฐ ์ ๊ฒ ๋ฐ ๋ณด์ ์กฐ์ธ
chronista-style
Chronistaใจใใฆๆดปๅใใใใใฎๅ ๆฌ็ในใญใซใปใใใๆฐธ็ถ่จๆถใ้็บใใญใผใใใญใฅใกใณใ็ฎก็ใใคใณใใฉใ็ตฑๅใ
ux-friction
Use when animation causes user confusion, delays task completion, or creates frustration
task-breakdown
Break complex features into delegatable tasks with clear ownership and dependencies. Use for feature planning phase.
