Search Results for "ilandahan" | AgentCC

aid-impl-plan

AID Phase 3 - Implementation Planning with a consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates a consolidated master document, then breaks it down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.

Learning Mode

Decision transparency, feedback collection, and invitations to debate for the AID methodology. Active in all phases for all roles.

aid-prd

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

atomic-page-builder

Build pages using ONLY existing Atomic Design components. REQUIRES Atomic Design skill. Use for composing pages and creating views/features from existing components.

role-product-manager

PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.

phase-enforcement

AID methodology phase gate enforcement. Ensures work follows the correct phase order (PRD -> Tech Spec -> Impl Plan -> Dev -> QA). Enforces gates and validates transitions.

Context Tracking

Real-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.

role-tech-lead

Tech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.

Figma Design Review

AI-powered design review for Figma components with a weighted dual-scoring system. Evaluates Style Guide Implementation (70%) and LLM Metadata Accessibility (30%). For export, hands off to the atomic-design skill.

aid-qa-ship

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, and operational readiness.

aid-development

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

AID Tech Spec

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, and for transitioning an approved PRD into implementation.

aid-discovery

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

System Architect

Senior System Architect for SaaS specifications. Security-first design with ISO 27001 compliance. Use for system architecture, tech specs, API design, technology choices, distributed systems, cloud infrastructure.

nano-banana-visual

[OPTIONAL] AI-powered visual generation using Google Nano Banana Pro. For user flows, architecture diagrams, and mockups.

why-driven-decision

FOUNDATIONAL SKILL - Analyze every prompt for underlying motivation using the Golden Circle (WHY->HOW->WHAT). Runs BEFORE any other skill. No action without understanding WHY.

test-driven

TDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, and Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.

Code Review

Comprehensive code review for commits and pull requests. Covers security, TDD, code quality, and documentation standards.

role-developer

Developer role in the AID methodology. Use for implementation, debugging, technical design, TDD workflow, and code review.

Atomic Design

Expert-level Atomic Design System development from Figma style guides. Build reusable component libraries with atoms, molecules, organisms, templates, and pages.

role-qa-engineer

QA Engineer role in AID methodology. Use for test strategy, BDD scenarios, bug reporting, acceptance testing, flaky test prevention.

Pre-PRD Research

Pre-PRD Research is a methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use it before writing any PRD to validate problems, conduct market research, perform competitive analysis, run stakeholder interviews, support ideation, and do root-cause analysis.