tool-roadmap-planner
Create phased implementation roadmaps for development tools, breaking them into MVP, enhancements, and polish phases with feature-level deliverables compatible with tool-feature-implementer.
Create phased implementation roadmaps for development tools, breaking them into MVP, enhancements, and polish phases with feature-level deliverables compatible with tool-feature-implementer.
Execute implementation plan by dispatching fresh subagent per task. Each task gets: Implementer → Spec Review → Quality Review. Two-stage review ensures both correctness and quality. Use this skill when: - Have implementation plan with multiple independent tasks - Want automated execution with quality gates after each task - Tasks are mostly independent (not tightly coupled) - User asks to "execute the plan", "run the tasks", "auto implement" Prerequisites: Must have plan from aico-*-plan or aico-*-task-breakdown skill. Process: For each task: Dispatch Implementer → Spec Review (passes?) → Quality Review (passes?) → Next task Review order: ALWAYS spec compliance first, THEN code quality.
Guide development of the whisper-lolo project based on specifications-projet.md. Use when planning or executing a sprint/PR, validating scope or constraints, or aligning architecture, statuses, and DoD for the Next.js + Vercel + Blob + Inngest + Whisper stack.
setup preparation readiness checklist pre-jam verification launch ready
Architecture and ADR workflows for Workbench CLI. Use when documenting system design, decisions, tradeoffs, or rationale that must be tracked over time.
Monitor CI/CD status for pull requests with error reporting. Triggers: "check CI", "CI status", "workflow status", "monitor CI", "检查CI", "CI状态", "查看构建".
Spawn 10-20 parallel agents for Leavn codebase audits, systematic fixes, comprehensive analysis across multiple domains simultaneously
Quality assurance workflow for PR reviews, CI pipeline monitoring, and production verification
Coordinates multi-component releases, feature flags, versioning, and rollback strategies. Trigger terms: release management, release planning, release coordination, feature flags, canary deployment, progressive rollout, release notes, rollback strategy, release train, deployment coordination, versioning, changelog, release approval, deployment checklist. Manages complex release workflows: - Multi-component release coordination - Feature flag strategy and management - Versioning and changelog generation - Canary and blue-green deployments - Progressive rollout strategies - Rollback procedures - Release approval workflows - Post-release verification Use when: planning releases, coordinating multi-service deployments, managing feature flags, or generating release notes.
Create a delivery roadmap that translates strategy into sequenced releases with milestones and dependencies.
Orchestrates Atlas workflow tier selection for software development tasks
Practice radical candor by delivering only verified, tested code with data-backed decisions, immediate problem flagging, and honest status communication. Use this skill when making claims about code behavior, reporting system status, identifying risks, documenting missing coverage, or challenging assumptions. Applies to all development activities requiring factual accuracy, evidence-based assertions, gap ownership, and closing the loop on delivered work through validation and independent review.
skill that dictates the deployment strategy for local development
Loads project context, lists existing specs and changes, searches capabilities and requirements. Use when user asks about project state, existing specs, active changes, available capabilities, or needs context discovery. Triggers include "what specs exist", "show changes", "list capabilities", "project context", "find specs", "what's in the spec", "show me specs".
Use after planning or implementing non-trivial tasks - runs Codex MCP background verification/review for quality gates (plan validation + implementation review)
Architecture and ADR workflows for Workbench CLI. Use when documenting system design, decisions, tradeoffs, or rationale that must be tracked over time.
Use the /review-plan slash command to validate scope, risks, and success criteria. Use when: gating plans before execution.
Critically review implementation plans before execution. Use when validating plans, checking standards compliance, or before running implement-plan.
Comprehensive development workflow specialist combining TDD, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
Apply triage decisions to SonarCloud security issues by reading a CSV with review decisions and updating issue/hotspot statuses via the SonarCloud API. Use when the user has reviewed security issues and wants to bulk-update SonarCloud with their triage decisions.
Orchestrate the full product flow from vision to shipped code. Use when starting a new feature or product.
Classify workflow failures and attempt automatic recovery. Use when sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.