cross-documentation-verification
Verify consistency and alignment across multiple documentation artifacts (epics, features, waves, ADRs, architecture docs) to detect conflicts, gaps, duplication, and misalignment. Identifies when new features contradict existing patterns, when ADRs conflict, when wave plans deviate from feature specifications, and when implementation docs drift from architecture. Use when finalizing features, before wave implementation, after architecture changes, during conformance reviews, or when detecting documentation drift.
do-workflow-spec
EARS 형식, 요구사항 명확화, Plan-Run-Sync 통합을 통한 SPEC workflow 오케스트레이션
meta-learning
This skill should be used when analyzing development sessions to extract learnings, determining what constitutes valuable knowledge to capture, creating skills from session insights, or evaluating whether patterns are worth codifying for reuse.
escalation-handler
Handles escalations and determines appropriate escalation paths. Use when issues arise that need escalation or when determining whether to escalate to user vs. handle internally. Analyzes issues, determines severity, and routes to appropriate resolution path.
aico-frontend-task-breakdown
Break down PM story into frontend tasks following UI DEVELOPMENT order: Setup → Static UI → Dynamic Logic → Interactions → Testing. UNIQUE VALUE: Ensures proper dependency order. Tasks are ordered by UI development layers, not random order. Use this skill when: - Running /frontend.tasks command - User asks to "break down story", "create frontend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task list - Need tasks ordered by UI development layers (not random order) - Starting frontend work and want organized task list Task order is CRITICAL: Setup → Static UI → Dynamic → Interactions → Tests Output: ALWAYS write to docs/reference/frontend/tasks/{story-name}.md
implementation-roadmap
Phased rollout plan for SDLC hardening. Foundation to runtime enforcement in 90 days. Prioritized by risk and audit importance.
general-development
General software development practices including code review, testing strategies, and CI/CD integration. Use when implementing features, writing tests, setting up deployment pipelines, or conducting peer reviews.
survey-cycle
HAIOS Survey Cycle for structured session-level work selection. Use after coldstart context loading. Guides GATHER->ASSESS->OPTIONS->CHOOSE->ROUTE workflow with volumous exploration before tight commitment.
project-manager
Project management expert specializing in planning, execution, monitoring, and closure of projects. Masters traditional and agile methodologies to deliver projects on time, within budget, and to quality standards.
start-task
Перед началом работы над любой задачей из папки docs\backlog и вложенных папок.
task-plan-skill
Use when starting a new feature that needs planning - runs brainstorming then creates numbered task folder in _tasks/
beads-task-create
Create a new Beads task (issue) with priority and (optional) type
scrum-master
Agile process facilitator specializing in Scrum framework implementation, team coaching, and continuous improvement. Masters servant leadership to unlock team potential and delivery excellence.
bead-workflow
Manage beads correctly including claiming, closing, announcements, and dependencies. Use when starting work on a task, when finishing a task, when the user mentions beads or tasks, or when coordinating with other agents on task ownership.
standardizing-dev-workflow
タスク実行をTaskfileで一元管理する標準開発フローを構築・監査。taskfile、aqua、lefthook、開発ワークフロー標準化、lint、format、git hooks、モノレポのセットアップや既存プロジェクトの監査時に使用。
implementation-postmortem
Conduct structured implementation postmortems to gather feedback on architecture conformance, library friction, and tooling effectiveness. Use when reviewing completed implementations, PRs, or development phases to surface design gaps, boundary violations, and improvement opportunities. Triggers on requests for code review feedback, implementation retrospectives, architecture audits, or library/tooling evaluations.
folder-org
Project code structure and file organization. Use when creating files, organizing components, or deciding where code should live. (project)
executing-plans
Use when you have a written implementation plan to execute - implements plan tasks in batches with review checkpoints between batches
review-linear-feature-requests
Review Linear issues tagged with "feature-request". Decide to spec, add to roadmap, merge, or reject. Triggers - review feature request, user request, customer feedback.
