ext-triage-java
Triage extension for Java findings during plan-finalize phase
Triage extension for Java findings during plan-finalize phase
Log work sessions with timestamps, decisions, agent handoffs, issues, and outcomes. Use when a session log needs to be created or updated.
ソフトウェアのリバースエンジニアリングレポートを作成するスキル。リポジトリの構造や機能を調査し、外部仕様・内部実装・使用方法を明確にするレポートを作成します。「リバースエンジニアリングレポートを作成して」「コードベースを分析して」「プロジェクトの構造を調査して」「システムの仕組みを解析して」等のリクエストで使用してください。新規開発者のオンボーディング、プロジェクトの理解、ドキュメント作成、将来の開発のための基礎資料として活用できます。
Review automation system operation and make conservative adjustments to cadences and thresholds when clearly warranted. Monthly maintenance task.
Creates spacing and sizing systems including margins, padding, gaps, and consistent spacing scales. Defines spacing tokens and usage guidelines for consistent layouts.
Validate Agent Skills against best practices and specification requirements. Use when reviewing skills, before publishing, or to audit existing skills.
Translate a finalized plan into Beads epics and issues with clear dependencies, design notes, and parallelization. Use when asked to file Beads from a plan/spec (OpenSpec, PRD, design doc), or when converting an external plan into a detailed Beads tracking structure.
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.
EARS 형식, 요구사항 명확화, Plan-Run-Sync 통합을 통한 SPEC workflow 오케스트레이션
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.
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.
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
Phased rollout plan for SDLC hardening. Foundation to runtime enforcement in 90 days. Prioritized by risk and audit importance.
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.
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 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.
Перед началом работы над любой задачей из папки docs\backlog и вложенных папок.
Use when starting a new feature that needs planning - runs brainstorming then creates numbered task folder in _tasks/
Create a new Beads task (issue) with priority and (optional) type
Agile process facilitator specializing in Scrum framework implementation, team coaching, and continuous improvement. Masters servant leadership to unlock team potential and delivery excellence.
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.