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 develo...
Découvrez les skills devops project management, comparez leurs dépôts et consultez leurs instructions.
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 develo...
Analyze feature requests and provide technical effort estimates with risk assessment
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: - Hav...
Create ATOMIC implementation plan for a single backend task. Each step has TDD, exact code, and verification command. IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For a...
Fetch and prioritize open GitHub issues for a repository. Use when managing GitHub issues, triaging bugs, prioritizing work, reviewing issue backlog, or when user asks to "triage issues", "show open issues", "p...
Execute backend implementation with TDD (Test-Driven Development). Write failing test first, then implement, verify each step. Use this skill when: - User asks to "implement this backend task", "implement back...
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 verifie...
convert structure outline into a detailed implementation plan
Diagnoses GitHub Actions CI/CD failures for FanHub's Node.js workflows. Identifies test failures, build errors, Docker issues, and environment problems.
Transform requirements into well-structured User Stories using "As a [user], I want [goal], So that [benefit]" format with Given/When/Then acceptance criteria. Use this skill when: - User asks to "write user s...
Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: -...
first step of planning
分析 GitHub Issue,判断类型和严重程度,定位 Bug 根因,自动修复简单问题。当 Issue 被创建或需要分析问题时使用。
Product Owner skill for managing product backlogs, user stories, roadmaps, requirements gathering, and stakeholder communication. Use when working with product strategy, feature prioritization, sprint planning,...
Review logs from ~/logs and remote log APIs to provide orientation and context for the day. Use when starting a work session, checking what happened recently, or needing context on recent activity. Reads daily...
Work on projects through well-defined specs. Spec-first approach with no ambiguity.
Strategic product planning skill for creating Product Requirements Documents (PRDs). This skill should be used when users want to plan new features, understand requirements, or create comprehensive product docu...
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Helps locate and navigate project documentation efficiently
This skill should be used when the user asks to "create a diagram", "draw a flowchart", "make a swimlane diagram", "create WBS", "generate RACI matrix", "build network diagram", "create org chart", or mentions...
Trello board, list and card management via CLI. Activate when user mentions "Trello" - examples: "Show my Trello tasks", "Add card to Trello", "Move on Trello", "Trello board", "List Trello", "Trello cards".
Guide users through writing effective task definitions for plan-forge. Use when user wants help writing a task, needs a task template, is preparing input for plan-forge, or asks "how do I write a good task for...
This skill should be used when the user asks to "generate tasks from a spec", "break down a spec", "create tasks from a PRD", "decompose requirements", "generate a task list from a design document", or mentions...
Manage development work using Jira tickets as the single source of truth. Use this skill when users want to (1) list their Jira tickets/work backlog, (2) create new Jira tickets/work items, (3) assign tickets t...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.