aico-pm-competitor-analysis

Research and analyze competitors with STRUCTURED output: feature comparison matrix, strengths/weaknesses analysis, and actionable recommendations. UNIQUE VALUE: Creates standardized competitor analysis document with feature matrix and strategic recommendations. Use this skill when: - User asks "what do competitors do?", "who are our competitors?" - User mentions competitor names or asks for product comparison - User asks for "competitor analysis", "market research", "competitive landscape" - Entering new market, feature area, or evaluating product direction - Need to understand competitive landscape before making product decisions - Writing PRD and need market context or differentiation strategy Output format: Feature comparison matrix + Strengths/Weaknesses + Actionable recommendations

Jump to install

Repository: yellinzero/aico
Last source activity: January 13, 2026 at 05:03
Detected SKILL.md language: English
Stars: 1
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/yellinzero/aico --skill aico-pm-competitor-analysis

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

aico-backend-implement

Execute backend task implementation with TDD. Read task file, execute steps, verify each, update status. Use this skill when: - User asks to "implement task/plan", "start implementation", "execute plan", or "start coding" - Have task file (story-* or standalone-*) ready to execute - User asks to "use TDD", "write test first", or "test-driven" - User asks to "write tests", "add tests", "create tests" - Fixing bugs (write failing test first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - Task file in docs/reference/backend/tasks/ (story-* or standalone-*) - Read constraints.md and design spec before coding Flow: Read Task → Read Constraints → Execute Steps → Verify → Test → Update Status

2026-02-12

aico-backend-plan

Create or enhance backend tasks with detailed implementation steps. Supports TWO modes: MODE A: Enhance existing task (add detailed steps to task in file) MODE B: Create new standalone task file (can contain single or multiple tasks) IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /backend.plan command - User asks for "atomic steps", "step-by-step plan with verification" - Have a specific task and need implementation steps - User wants to create a standalone task file (not from story) - Need granular steps: Types → DB → Repository → Service → API → Tests DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: - MODE A: Update specific task section in file with Implementation Steps - MODE B: Create new standalone-{name}.md file with one or multiple tasks

2026-02-12

aico-backend-task-breakdown

Break down PM story into organized tasks in a single file following LAYERED ARCHITECTURE order: Types → Database → Repository → Service → API → Tests. UNIQUE VALUE: Creates single task file (story-{name}.md) containing all tasks for a story. Tasks are ordered by backend architecture layers. Use this skill when: - Running /backend.tasks command - User asks to "break down story", "create backend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task breakdown - Need tasks ordered by backend architecture layers (not random order) - Starting backend work and want organized task list Task order is CRITICAL: Types → Database → Repository → Service → API → Tests Output: Create single file docs/reference/backend/tasks/story-{name}.md with all tasks

2026-02-12

View all from this repository

name

aico-pm-competitor-analysis

description

Competitor Analysis

Language Configuration

Before generating any content, check aico.json in project root for language field to determine the output language. If not set, default to English.

Process

Identify competitors: Direct and indirect
Create feature matrix: Compare capabilities
Analyze each competitor: Strengths, weaknesses, positioning
Identify market gaps: Opportunities for differentiation
Develop recommendations: Actionable strategies

Analysis Document Template

# Competitor Analysis: [Product Area]

## Executive Summary

[2-3 sentence overview of findings]

## Competitors Overview

| Competitor | Type     | Target Users | Key Strength |
| ---------- | -------- | ------------ | ------------ |
| [Name]     | Direct   | [Users]      | [Strength]   |
| [Name]     | Indirect | [Users]      | [Strength]   |

## Feature Comparison

| Feature     | Us    | Competitor A | Competitor B |
| ----------- | ----- | ------------ | ------------ |
| [Feature 1] | ✓/✗/- | ✓/✗/-        | ✓/✗/-        |

Legend: ✓ Has / ✗ Doesn't have / - Partial

## Detailed Analysis

### [Competitor Name]

- **Strengths**: [What they do well]
- **Weaknesses**: [Where they fall short]
- **Positioning**: [How they position themselves]

## Opportunities

### Gaps in Market

- [Gap 1]: [How we can address]

### Differentiation Strategies

- [Strategy 1]

## Recommendations

- [Actionable recommendation based on analysis]

Research Sources

Product websites and documentation
User reviews (G2, Capterra, etc.)
Social media and community feedback
Direct product trials

Key Rules

ALWAYS include both direct and indirect competitors
MUST create feature comparison matrix
ALWAYS end with actionable recommendations
Include positioning and strategy, not just features

Common Mistakes

❌ Only direct competitors → ✅ Include indirect/adjacent
❌ Feature-only focus → ✅ Include positioning/strategy
❌ No recommendations → ✅ Always end with actions

aico-pm-competitor-analysis

Source facts

Install options

Review the source files

More from this repository

More from this repository

Competitor Analysis

Language Configuration

Process

Analysis Document Template

Research Sources

Key Rules

Common Mistakes

Competitor Analysis

Language Configuration

Process

Analysis Document Template

Research Sources

Key Rules

Common Mistakes