MACCA-METHOD

Skill for adding new features to running projects. Read existing specs, identify all affected documents, mandatory update of all impacted specs, then add phase and tasks to Task.md.

Skill to interview user and generate api.md (Endpoint Documentation / API Contract). Use after schema.md is complete to document all API endpoints.

Skill to interview user and generate architecture.md (System Architecture). Use after PRD is complete to define tech stack, structure, and architectural decisions.

Skill to interview user and generate PRD.md (Product Requirements Document) interactively. Use when creating a PRD or starting a new project.

Interview-driven skill to generate rules.md (Coding Standards / Code Constitution). Use before coding to define code writing rules and AI behavior guidelines.

Skill to interview user and generate schema.md (Data Model / Database Schema). Use after architecture.md is complete.

Interview-driven skill to generate StyleGuide.md (UI/UX Design System). Use after PRD or when defining application appearance.

Automatically generate Task.md (Work Breakdown Plan) from completed spec documents. Run after PRD, Architecture, Schema, API, and Rules are finished.

Diagnose, fix, and document bugs. Check bug-log.md first to recognize similar patterns. Record to bug-log only after user confirms the fix is correct.

Review code quality and security after each phase. Run after spec-compliance. Includes 27-item code quality checklist and security essentials (injection, auth, XSS, authorization, API security).

Execute tasks from Task.md phase by phase. Developer reads relevant specs, writes code, updates Task.md, and runs spec-compliance + code-review automatically after each phase completes.

Interactive guide to the AI Spec-Driven Development system. Detects current project state, recommends next steps, explains each skill, and answers workflow questions.

Skill for conducting team discussion sessions. Galbi facilitates, introduces selected team members, opens free discussion where each persona can be called by name for their perspective.

Skill to check consistency between project-context/ documents or between MACCA framework documents themselves. Detects conflicts, inconsistencies, and ambiguities across documents—not within them. Reports where the problem is, why it matters, and the specific fix with reasoning.

Verify that code aligns with all project spec documents (PRD.md, architecture.md, schema.md, api.md, rules.md, StyleGuide.md, Task.md). Run after each phase completes, before code-review.

Generate all project-context/ documents from an existing codebase. Supports Batch Generate (all at once) or Guided Generate (one-by-one with confirmation). Suitable for running projects or boilerplates.