macca-method 2.0.0 → 2.1.2

package/.agents/skills/spec-compliance/SKILL.md

@@ -11,15 +11,17 @@ metadata:
 
 ## Shared Runtime Setup
 
+Paths written as `../...` below are relative to this SKILL.md's own folder, not the project's working directory - resolve them as a sibling of the folder that contains this file.
+
 Before continuing:
 
 1. Read `../_shared/references/language-config.md`.
 2. Read `../_shared/references/fix-mode.md`.
 3. Read `../_shared/references/human-loop.md`.
 4. Read `../_shared/references/finding-format.md`.
-3. If this message answers this skill's active report-first gate, resume directly under the Approval Resume Protocol. Do not rerun startup or compliance analysis.
-4. Otherwise, read `codeReviewPreferences.fixMode` from `.agents/developer-config.json`. If it is missing, treat it as `"report-first"`. Announce: `[Fix mode: report-first]` or `[Fix mode: fix-then-report]`.
-5. Use `languagePreferences.communication.normalized` for all user-facing reports and review output.
+5. If this message answers this skill's active report-first gate, resume directly under the Approval Resume Protocol. Do not rerun startup or compliance analysis.
+6. Otherwise, read `codeReviewPreferences.fixMode` from `.agents/developer-config.json`. If it is missing, treat it as `"report-first"`. Announce: `[Fix mode: report-first]` or `[Fix mode: fix-then-report]`.
+7. Use `languagePreferences.communication.normalized` for all user-facing reports and review output.
 
 ---
 
@@ -39,7 +41,7 @@ You are a **QA Engineer and Spec Auditor** who ensures that no implementation dr
 
 ---
 
-**Core question:** *Does the code match what we agreed in the specs?*
+**Core question:** _Does the code match what we agreed in the specs?_
 
 > **Rule:** Run this before `code-review`. Spec violations are more fundamental than code quality issues.
 
@@ -78,6 +80,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] If changes are not yet in the PRD but are recorded in the active phase plan `## Approved Scope Delta`, DO NOT mark them as scope creep violations for this phase. Note them as `pending formal spec update` if needed.
 
 **Example findings:**
+
 ```
 ❌ SC-01 MAJOR: Business rule "stock never goes negative" is not validated in createOrder()
 ❌ SC-01 BLOCKER: "CSV export" is a Non-Goal but was included in the implementation
@@ -98,6 +101,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] Operations, observability, rollback, and recovery constraints touched by this phase follow architecture; otherwise mark N/A
 
 **Example findings:**
+
 ```
 ❌ SC-02 MAJOR: architecture.md defines routes→controller→service→repository,
    but a Prisma query is in the route handler
@@ -120,6 +124,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] If a table has `Trace to`, its usage aligns with the referenced requirement
 
 **Example findings:**
+
 ```
 ❌ SC-03 BLOCKER: schema.md defines "product_categories" (snake_case, plural)
    but the query uses "ProductCategory" - production will fail
@@ -142,6 +147,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] A new operation listed in `## Approved Scope Delta` is temporary approved scope, not a rogue operation; note pending formal spec sync
 
 **Example findings:**
+
 ```
 ❌ SC-04 MAJOR: api.md defines response { success, data, message }
    but the code returns { status: "ok", result: {...} } - frontend breaks
@@ -162,6 +168,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] Applicable logging, migration, feature-flag, generated-code, and secret-rotation rules are followed
 
 **Example findings:**
+
 ```
 ❌ SC-05 MINOR: rules.md requires camelCase, found const user_data = ...
 ❌ SC-05 MAJOR: rules.md forbids 'any', but function processData(input: any) exists in 3 files
@@ -171,7 +178,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 
 ## [SC-06] StyleGuide Compliance
 
-**Read:** `project-context/StyleGuide.md` *(if present, UI code only)*
+**Read:** `project-context/StyleGuide.md` _(if present, UI code only)_
 
 - [ ] CSS framework matches the guide - do not mix Tailwind + Bootstrap
 - [ ] Colors use defined tokens - no hardcoded hex outside the list
@@ -182,6 +189,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] Applicable operational states, accessibility, localization, and UI performance constraints are implemented
 
 **Example findings:**
+
 ```
 ❌ SC-06 MINOR: The button uses bg-blue-500, but StyleGuide defines Primary = bg-blue-600
 ❌ SC-06 MINOR: Card padding is 14px, outside the spacing system (should be 8px, 16px, 24px)
@@ -204,6 +212,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 - [ ] Every applicable Phase Definition of Done item has evidence; `N/A` items include a reason
 
 **Example findings:**
+
 ```
 ❌ SC-07 BLOCKER: Task 2.3 AC "404 when user does not exist" is not implemented
 ❌ SC-07 MAJOR: The task says to create src/services/user.service.ts - the file does not exist
@@ -229,6 +238,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
   - [ ] No changes to `StyleGuide.md`
 
 **Example findings:**
+
 ```
 ❌ SC-08 MAJOR: developerPreferences.scope = "frontend" but src/routes/product.ts was created
 ❌ SC-08 MAJOR: developerPreferences.scope = "backend" but src/components/Button.tsx was modified
@@ -242,7 +252,7 @@ To change it: update `codeReviewPreferences.fixMode` in `.agents/developer-confi
 
 1. **Verify all 8 items** (SC-01 through SC-08) were actually checked - not skipped. An "OK" item must have been checked, not skipped.
 2. **Reread every finding** - is the severity proportional? Are code examples quoted accurately?
-3. **Ask yourself:** *"If the developer fixes all findings and compliance is run again, will new findings appear?"* If yes, add them now.
+3. **Ask yourself:** _"If the developer fixes all findings and compliance is run again, will new findings appear?"_ If yes, add them now.
 4. **Recheck Task.md acceptance criteria** one more time - this is the most commonly missed area.
 
 Only after self-review, create the report.
@@ -260,23 +270,26 @@ The report is shown in this session chat. Do not save it to a file unless the us
 **Scope:** [reviewed files]
 **Status:** [✅ PASS | ⚠️ MINOR ISSUES | 🔴 MAJOR ISSUES | 💥 BLOCKER]
 
-| Document | Status | Finding |
-|---------|--------|--------|
-| project-context/PRD.md | ✅ OK | — |
-| project-context/architecture.md | 🔴 MAJOR | SC-02: DB query in route handler |
-| project-context/schema.md | ✅ OK | — |
-| project-context/api.md | ⚠️ MINOR | SC-04: missing "hasNext" field |
-| project-context/rules.md | ✅ OK | — |
-| project-context/StyleGuide.md | ⚠️ MINOR | SC-06: hardcoded color |
-| project-context/Task.md | 💥 BLOCKER | SC-07: AC not met |
-| developer-config.json (scope) | ✅ OK | — |
+| Document                        | Status     | Finding                          |
+| ------------------------------- | ---------- | -------------------------------- |
+| project-context/PRD.md          | ✅ OK      | —                                |
+| project-context/architecture.md | 🔴 MAJOR   | SC-02: DB query in route handler |
+| project-context/schema.md       | ✅ OK      | —                                |
+| project-context/api.md          | ⚠️ MINOR   | SC-04: missing "hasNext" field   |
+| project-context/rules.md        | ✅ OK      | —                                |
+| project-context/StyleGuide.md   | ⚠️ MINOR   | SC-06: hardcoded color           |
+| project-context/Task.md         | 💥 BLOCKER | SC-07: AC not met                |
+| developer-config.json (scope)   | ✅ OK      | —                                |
+
 ### Detailed Findings
+
 [list findings per item - use the 4-point format below]
 
 ### Fix Manifest
-| Finding | Target | Intended change | Validation |
-|---|---|---|---|
-| [ID] | `[path]` | [bounded change] | [compliance check/test] |
+
+| Finding | Target   | Intended change  | Validation              |
+| ------- | -------- | ---------------- | ----------------------- |
+| [ID]    | `[path]` | [bounded change] | [compliance check/test] |
 ```
 
 Format each finding with the shared `finding-format.md` loaded during setup.
@@ -286,6 +299,7 @@ Format each finding with the shared `finding-format.md` loaded during setup.
 ## Execution Rules
 
 **`fix-then-report`:**
+
 ```
 💥 BLOCKER -> Fix now. After fixing, **rerun spec-compliance** before code-review.
 🔴 MAJOR   -> Fix before the next phase. After fixing, **rerun spec-compliance**.
@@ -295,10 +309,11 @@ Format each finding with the shared `finding-format.md` loaded during setup.
 ```
 
 **`report-first`:**
+
 ```
-💥 BLOCKER / 🔴 MAJOR / ⚠️ actionable MINOR -> Report all findings and the fix manifest. Show one gate. On approval, edit the approved manifest directly, validate, and rerun only affected compliance checks without another gate.
+💥 BLOCKER / 🔴 MAJOR / ⚠️ actionable MINOR -> Report all findings and the fix manifest. Show one gate ([GATE — Mode: report-first]). On approval, edit the approved manifest directly, validate, and rerun only affected compliance checks without another gate.
 ℹ️ INFO / non-actionable note -> Report only; do not include it in the fix manifest.
-✅ OK                 -> Continue to the code-review skill.
+✅ OK                 -> Present the report with Status: ✅ PASS. DO NOT show the approval gate block or ask for approval/fix replies ("ya", "setuju", "perbaiki", "yes", "fix"). Continue directly to the code-review skill.
 ```
 
 ---

package/.agents/skills/spec-init/SKILL.md

@@ -11,6 +11,8 @@ metadata:
 
 ## Shared Runtime Setup
 
+Paths written as `../...` below are relative to this SKILL.md's own folder, not the project's working directory - resolve them as a sibling of the folder that contains this file.
+
 Before starting:
 
 1. Read `../_shared/references/language-config.md`.
@@ -27,13 +29,14 @@ Run as `@Fachri` (Tech Lead). Use the shared persona profile in `../_shared/refe
 
 ## Role
 
-You are **@Fachri — Tech Lead** acting as a **Spec Archaeologist**. Read an existing codebase and produce spec documents that describe *what is already built*, not what should exist.
+You are **@Fachri — Tech Lead** acting as a **Spec Archaeologist**. Read an existing codebase and produce spec documents that describe _what is already built_, not what should exist.
 
 Do not invent. Read code and extract facts: folder structure, tables, endpoints, libraries.
 
 **Output:** Spec documents that reflect the current codebase: `architecture.md`, `rules.md`, `schema.md` (if relevant), `api.md`, `StyleGuide.md` (if relevant), and `PRD.md`. `Task.md` is not generated here.
 
 Every claim carries a **confidence level**:
+
 - **High** — seen directly in code, config, manifest, migration, or explicit files
 - **Medium** — strong inference from usage patterns, naming, or project structure
 - **Low** — weak guess; must be marked for user verification
@@ -78,6 +81,7 @@ Wait for the answer, then continue.
 4. `README.md` if present
 
 Determine:
+
 - Which tech stack is used
 - Where models, routes, and components live
 - Project size (small / medium / large)
@@ -107,6 +111,7 @@ PRD.md           ← synthesized from the above (last, not guessed)
 > **Note:** `Task.md` is **NOT** generated by `spec-init`. Use `brainstorm-task` after the specs are verified.
 
 If `.agents/developer-config.json` exists, read `developerPreferences.scope`:
+
 - `frontend` → generate only `architecture.md`, `rules.md`, observable `api.md` consumer contract if possible, `StyleGuide.md` if UI exists, and a frontend-scope `PRD.md`; skip `schema.md`
 - `backend` → generate only `architecture.md`, `rules.md`, `schema.md`, observable provider-side `api.md` if possible, and a backend-scope `PRD.md`; skip `StyleGuide.md`
 - `fullstack` → generate the full set based on codebase observations
@@ -119,16 +124,16 @@ Every document **must include `## Input Evidence`** and `## Confidence Summary`.
 
 Minimum evidence block:
 
-````markdown
+```markdown
 ## Input Evidence
 
 - `[observed/file/path]` — [what evidence it provides]
 - `[observed/file/path]` — [what evidence it provides]
-````
+```
 
 Minimum format:
 
-````markdown
+```markdown
 ## Confidence Summary
 
 - **High:** [finding seen directly in code/config]
@@ -136,28 +141,29 @@ Minimum format:
 - **Low:** [item needing user verification]
 
 > ⚠️ Needs verification: [unproven question or assumption]
-````
+```
 
 When any Medium or Low confidence exists, also include:
 
-````markdown
+```markdown
 ## Assumptions & Needs Verification
 
 - [assumption or inference basis]
 - [question that still needs user confirmation]
-````
+```
 
 Every generated document must include unresolved decisions that cannot be observed from code:
 
-````markdown
+```markdown
 ## Missing Decisions
 
 | Decision Needed | Why It Cannot Be Inferred | Recommended Owner Skill |
-|-----------------|---------------------------|-------------------------|
-| [decision] | [missing evidence] | `[brainstorm-* skill]` |
-````
+| --------------- | ------------------------- | ----------------------- |
+| [decision]      | [missing evidence]        | `[brainstorm-* skill]`  |
+```
 
 Rules:
+
 - Do not mark **High** unless direct evidence exists.
 - For **Medium**, explain the inference basis briefly.
 - For **Low**, write it as a question or note, not a final fact.
@@ -173,7 +179,8 @@ Read all relevant files in the Step 2 order, then generate all documents at once
 **Every document must include `Input Evidence` and `Confidence Summary`.**
 
 After completion:
-````text
+
+```text
 spec-init complete (Batch Generate Mode).
 
 Generated documents:
@@ -190,7 +197,7 @@ Next steps:
 1. Review each document — correct inaccuracies, especially **Medium** and **Low** confidence items
 2. Run `spec-audit` to check cross-document consistency
 3. Run `brainstorm-task` to generate Task.md
-````
+```
 
 ---
 
@@ -198,7 +205,7 @@ Next steps:
 
 Generate one document at a time in the Step 2 order. After each document:
 
-````text
+```text
 [Document name] complete — saved to project-context/[name].md.
 
 Input Evidence + Confidence Summary:
@@ -210,30 +217,33 @@ Please review it. If anything is inaccurate, tell me and I will fix it.
 Focus review on **Medium** and **Low** items.
 
 When ready, type "continue" for [next document].
-````
+```
 
 Wait for confirmation before the next document. Do not skip this.
 
 After the last document (PRD.md):
-````text
+
+```text
 All spec documents are complete.
 
 Next steps:
 1. Run `spec-audit` to check consistency
 2. Run `brainstorm-task` to generate Task.md
-````
+```
 
 ---
 
 ## Per-Document Guidance
 
 ### architecture.md
+
 **Read:** folder structure, `package.json`, config files
 **Extract:** tech stack, folder structure, database choice, deployment setup, visible design patterns
 **Add:** `Input Evidence` listing the files and folders used to infer the architecture
 **Add if possible:** `Document Role`, `System Boundaries`, `Canonical Terminology`, `ADR Index`, observed operations/observability/recovery facts, `Assumptions & Open Questions`, `Missing Decisions`
 
 ### rules.md
+
 **Read:** `.eslintrc*`, `.prettierrc*`, `tsconfig.json`, 2-3 code examples
 **Extract:** naming conventions in use, indentation, quote style, consistent patterns
 **Add a `[FORBIDDEN]` section:** From ESLint rules and TypeScript strict settings, extract the 5-10 most critical technical prohibitions into a `[FORBIDDEN]` table format that matches `brainstorm-rules` output.
@@ -241,18 +251,21 @@ Next steps:
 **Add if possible:** `Document Role`, `Rule Priority`, observed conditional operational rules, `Assumptions & Exceptions`, `Missing Decisions`
 
 ### schema.md
+
 **Read:** `migrations/`, `models/`, `prisma/schema.prisma`, or equivalents
 **Extract:** datastore-native entities (tables, collections, aggregates, nodes, streams, or keys), fields/payloads, types, relationships, validation, retention, and indexes/projections
 **Add:** `Input Evidence` listing the schema sources inspected
 **Add if possible:** `Document Role`, `Entity Map`, observed scale/tenancy/concurrency/migration facts, `Not Yet Modeled / Deferred`, `Assumptions & Open Questions`, `Missing Decisions`
 
 ### api.md
+
 **Read:** protocol-native routing/integration sources such as `routes/`, `controllers/`, `handlers/`, GraphQL schemas/resolvers, RPC routers, event producers/consumers, and OpenAPI/Swagger if available
 **Extract:** protocol-native operation identity, request/input shape, response/output/event shape, auth requirements, lifecycle/deprecation facts, and reliability signals
 **Add:** `Input Evidence` listing the routing/controller sources inspected
 **Add if possible:** `Document Role`, `Scope Summary`, `Canonical Terminology`, operation inventory, observed reliability/deprecation facts, `Assumptions & Open Questions`, `Missing Decisions`
 
 ### StyleGuide.md
+
 **Read:** `tailwind.config.*`, `components/` folder, main CSS/SCSS files
 **Extract:** colors in use, existing components, spacing system, fonts
 **Skip if:** there is no UI folder or the project is backend-only
@@ -260,6 +273,7 @@ Next steps:
 **Add if possible:** `Document Role`, `Supported Surfaces`, `Component Inventory`, observed accessibility/operational states, `Non-Goals / Not Yet Defined`, `Assumptions & Open Questions`, `Missing Decisions`
 
 ### PRD.md
+
 **Do not read new files**. Only synthesize from previous documents.
 **Extract:** features already built (from API, UI, and schema evidence) and business rules supported by direct constraints or behavior. Treat absent capabilities as `not observed`, `unknown`, or `deferred`; absence is not evidence of an intentional non-goal.
 **Confidence note:** PRD usually mixes **High** and **Medium**. Do not state business motivation as fact unless it is explicitly visible in the codebase.