macca-method 2.0.0 → 2.1.2

package/.agents/macca-lock.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0",
+  "version": "2.1.2",
   "skills": [
     "_shared",
     "add-feature",

package/.agents/skills/_shared/references/brainstorm-session.md

@@ -84,11 +84,11 @@ When a brainstorming skill starts:
 2. Read `brainstormPreferences` if present.
 3. **Announce the session** before asking anything:
    - If preferences are already saved, announce and proceed in the same response. The user may override them at any time:
-      ```
-      This session has [N] topics.
-      Saved preferences: [pacing] | recommendations: [on/off] | depth: [quick/standard/critical]
-      Using these settings. Type different settings at any time.
-      ```
+     ```
+     This session has [N] topics.
+     Saved preferences: [pacing] | recommendations: [on/off] | depth: [quick/standard/critical]
+     Using these settings. Type different settings at any time.
+     ```
    - If no preferences are saved — ask both before starting:
      ```
      This session has [N] topics. Two things before we start:

package/.agents/skills/_shared/references/fix-mode.md

@@ -11,7 +11,20 @@ Announce `[Fix mode: report-first]` or `[Fix mode: fix-then-report]` at the star
 
 ## Required Report-First Gate
 
-After the full report and fix manifest, print this block verbatim and end the response:
+After the full report and fix manifest, print the block below matching `languagePreferences.communication.normalized` (see `language-config.md`) and end the response. Use only one language block - never mix English and Indonesian inside it.
+
+Indonesian (`indonesian`, `id`, and any equivalent listed in `language-config.md` - also the default when the preference is missing or unrecognized):
+
+```text
+---
+[GATE — Mode: report-first]
+Semua temuan sudah dilaporkan. Belum ada file yang diubah.
+Balas "ya" / "setuju" / "lanjut" / "perbaiki" untuk menerapkan semua perbaikan,
+atau sebutkan temuan mana saja yang ingin diperbaiki.
+---
+```
+
+English (`english`, `en`):
 
 ```text
 ---
@@ -29,8 +42,10 @@ The fix manifest records each actionable finding ID, target, bounded change, and
 This takes precedence over normal routing, startup, identity, onboarding, preflight, and work-mode prompts.
 
 1. Trim and case-fold the next response.
-2. Exact `yes`, `fix`, or `continue` approves every actionable finding in the immediately preceding report, including actionable MINOR findings.
-3. Named IDs approve only those findings.
+2. Any of these approves every actionable finding in the immediately preceding report, including actionable MINOR findings:
+   - English: `yes`, `fix`, `continue`
+   - Indonesian: `ya`, `iya`, `setuju`, `lanjut`, `perbaiki`
+3. Named IDs approve only those findings, in either language.
 4. Resume directly at edits. Do not repeat analysis, the report, startup, preflight, or the same gate.
 5. Ask again only if the worktree changed materially, a target disappeared, findings conflict, or the implementation becomes destructive or exceeds disclosed scope.
 6. Run the narrowest relevant validation and one bounded verdict pass: `resolved`, `partial`, or `unresolved`.

package/.agents/skills/_shared/references/human-loop.md

@@ -54,4 +54,4 @@ Keep one decision topic per pause.
 
 After the user answers, continue from the exact paused step. Do not restart the workflow or ask for the same confirmation again unless the situation materially changes.
 
-An answer to an active gate takes precedence over normal skill startup and routing. For a report-first gate, exact `yes`, `fix`, or `continue` and finding-ID subsets follow the Approval Resume Protocol in `fix-mode.md`. Do not send them through identity setup, preflight, or a second confirmation.
+An answer to an active gate takes precedence over normal skill startup and routing. For a report-first gate, the approval tokens and finding-ID subsets defined in `fix-mode.md`'s Approval Resume Protocol take priority. Do not send them through identity setup, preflight, or a second confirmation.

package/.agents/skills/_shared/references/invocation-policy.md

@@ -4,26 +4,26 @@ This catalog documents intent; it does not replace host routing or safety gates.
 
 Portable Agent Skills rely on `name` and `description`. OpenCode ignores Copilot-specific invocation fields. Therefore canonical skills keep standard frontmatter and express routing through descriptions and workflow boundaries.
 
-| Skill | Policy | Rationale |
-|---|---|---|
-| `add-feature` | explicit-intent | Broad source-of-truth mutation |
-| `brainstorm-prd` | explicit-intent | Long interview and PRD creation |
-| `brainstorm-architecture` | explicit-intent | Strategic technical decisions |
-| `brainstorm-schema` | explicit-intent | Consequential data contract |
-| `brainstorm-api` | explicit-intent | External contract creation |
-| `brainstorm-styleguide` | explicit-intent | UI contract interview |
-| `brainstorm-rules` | explicit-intent | Repository-wide rules |
-| `brainstorm-task` | both | Direct use and `add-feature` orchestration |
-| `spec-init` | explicit-intent | Whole-codebase scan and multi-document generation |
-| `developer` | explicit-implementation-intent | Broad implementation mutation |
-| `quick-dev` | model-auto | Bounded router for small implementation tasks |
-| `bug-fix` | both | Automatic bug/error routing and direct use; the first code change still requires explicit implementation approval from the diagnosis gate |
-| `spec-compliance` | orchestrated | Called by execution/remediation workflows; ad hoc requests remain valid |
-| `code-review` | both | Direct review and post-phase orchestration |
-| `spec-audit` | both | Direct audit and final workflow check |
-| `release-readiness` | both | Direct pre-release request and project-complete handoff |
-| `help` | both | Cheap read-only routing |
-| `meet` | both | Non-mutating meeting intent |
+| Skill                     | Policy                         | Rationale                                                                                                                                 |
+| ------------------------- | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `add-feature`             | explicit-intent                | Broad source-of-truth mutation                                                                                                            |
+| `brainstorm-prd`          | explicit-intent                | Long interview and PRD creation                                                                                                           |
+| `brainstorm-architecture` | explicit-intent                | Strategic technical decisions                                                                                                             |
+| `brainstorm-schema`       | explicit-intent                | Consequential data contract                                                                                                               |
+| `brainstorm-api`          | explicit-intent                | External contract creation                                                                                                                |
+| `brainstorm-styleguide`   | explicit-intent                | UI contract interview                                                                                                                     |
+| `brainstorm-rules`        | explicit-intent                | Repository-wide rules                                                                                                                     |
+| `brainstorm-task`         | both                           | Direct use and `add-feature` orchestration                                                                                                |
+| `spec-init`               | explicit-intent                | Whole-codebase scan and multi-document generation                                                                                         |
+| `developer`               | explicit-implementation-intent | Broad implementation mutation                                                                                                             |
+| `quick-dev`               | model-auto                     | Bounded router for small implementation tasks                                                                                             |
+| `bug-fix`                 | both                           | Automatic bug/error routing and direct use; the first code change still requires explicit implementation approval from the diagnosis gate |
+| `spec-compliance`         | orchestrated                   | Called by execution/remediation workflows; ad hoc requests remain valid                                                                   |
+| `code-review`             | both                           | Direct review and post-phase orchestration                                                                                                |
+| `spec-audit`              | both                           | Direct audit and final workflow check                                                                                                     |
+| `release-readiness`       | both                           | Direct pre-release request and project-complete handoff                                                                                   |
+| `help`                    | both                           | Cheap read-only routing                                                                                                                   |
+| `meet`                    | both                           | Non-mutating meeting intent                                                                                                               |
 
 Definitions:
 

package/.agents/skills/_shared/references/language-config.md

@@ -4,12 +4,14 @@ Read `.agents/developer-config.json` if it exists.
 
 Use:
 
-- `languagePreferences.communication.normalized` for chat, reports, prompts, and confirmations.
+- `languagePreferences.communication.normalized` for chat, reports, prompts, confirmations, and gate/approval text.
 - `languagePreferences.documents.normalized` for generated project documents.
 
-Accepted reader values:
+When the resolved language is Indonesian, all chat output - including report-first gates and their reply options - MUST be Indonesian. Do not mix in English sentences or fall back to English-only reply tokens.
 
-- Indonesian: `indonesian`, `id`
-- English: `english`, `en`
+Match `raw` or `normalized` case-insensitively against these equivalents (same mapping the installer's `normalizeLanguage()` uses):
 
-If missing, use Indonesian. Never translate file names, traceability IDs, config keys, or code literals.
+- Indonesian: `indonesian`, `id`, `indo`, `indonesia`, `bahasa indonesia`
+- English: `english`, `en`, `eng`, `inggris`, `bahasa inggris`
+
+If missing or unrecognized, use Indonesian. Never translate file names, traceability IDs, config keys, or code literals.

package/.agents/skills/_shared/references/output-ownership.md

@@ -6,17 +6,17 @@ This file defines which skill primarily owns each persistent output, so skills d
 
 ## Primary Owners
 
-| Output | Primary Owner | Secondary / Limited Authors |
-|---|---|---|
-| `project-context/PRD.md` | `brainstorm-prd` | `add-feature`, `spec-init` |
-| `project-context/architecture.md` | `brainstorm-architecture` | `add-feature`, `spec-init` |
-| `project-context/schema.md` | `brainstorm-schema` | `add-feature`, `spec-init` |
-| `project-context/api.md` | `brainstorm-api` | `add-feature`, `spec-init` |
-| `project-context/StyleGuide.md` | `brainstorm-styleguide` | `add-feature`, `spec-init` |
-| `project-context/rules.md` | `brainstorm-rules` | `add-feature`, `spec-init` |
-| `project-context/Task.md` | `brainstorm-task` | `developer` updates progress and approved phase deltas; `quick-dev` adds one approved lightweight entry; `add-feature` hands off to `brainstorm-task` |
-| `project-context/bug-log.md` | `bug-fix` | none |
-| `project-context/plans/*.md` | `developer` | `add-feature`, `code-review` limited updates per workflow |
+| Output                            | Primary Owner             | Secondary / Limited Authors                                                                                                                                                                      |
+| --------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `project-context/PRD.md`          | `brainstorm-prd`          | `add-feature`, `spec-init`                                                                                                                                                                       |
+| `project-context/architecture.md` | `brainstorm-architecture` | `add-feature`, `spec-init`                                                                                                                                                                       |
+| `project-context/schema.md`       | `brainstorm-schema`       | `add-feature`, `spec-init`                                                                                                                                                                       |
+| `project-context/api.md`          | `brainstorm-api`          | `add-feature`, `spec-init`                                                                                                                                                                       |
+| `project-context/StyleGuide.md`   | `brainstorm-styleguide`   | `add-feature`, `spec-init`                                                                                                                                                                       |
+| `project-context/rules.md`        | `brainstorm-rules`        | `add-feature`, `spec-init`                                                                                                                                                                       |
+| `project-context/Task.md`         | `brainstorm-task`         | `developer` updates progress and approved phase deltas; `quick-dev` adds one approved lightweight entry; `add-feature` adds approved phase deltas (or hands off to `brainstorm-task` if missing) |
+| `project-context/bug-log.md`      | `bug-fix`                 | none                                                                                                                                                                                             |
+| `project-context/plans/*.md`      | `developer`               | `add-feature`, `code-review` limited updates per workflow                                                                                                                                        |
 
 ## Ownership Rules
 

package/.agents/skills/_shared/references/scope-rules.md

@@ -9,7 +9,7 @@ This file defines how skills must adjust documents, recommendations, and work bo
 - `frontend`
 - `backend`
 - `fullstack`
-- *(missing)* → treat as `fullstack`
+- _(missing)_ → treat as `fullstack`
 
 ## General Rules
 

package/.agents/skills/_shared/references/skill-catalog.md

@@ -2,26 +2,26 @@
 
 Compact framework-audit index. This is not a replacement for each `SKILL.md`; it identifies which full files need inspection when a conflict is suspected.
 
-| Skill | Invocation | Reads | Writes / Output | Primary Handoff |
-|---|---|---|---|---|
-| `brainstorm-prd` | explicit-intent | scope/config, user discovery | `PRD.md` | `brainstorm-architecture` |
-| `brainstorm-architecture` | explicit-intent | PRD | `architecture.md` | schema/API/style/rules |
-| `brainstorm-schema` | explicit-intent | PRD, architecture | `schema.md` | `brainstorm-api` |
-| `brainstorm-api` | explicit-intent | PRD, architecture, schema when applicable | `api.md` | style/rules/task |
-| `brainstorm-styleguide` | explicit-intent | PRD, architecture | `StyleGuide.md` | rules/task |
-| `brainstorm-rules` | explicit-intent | architecture and applicable domain specs | `rules.md` | `brainstorm-task` |
-| `brainstorm-task` | both | applicable specs | `Task.md` | `developer` |
-| `add-feature` | explicit-intent | all existing specs | approved spec deltas; delegates Task | `developer` |
-| `spec-init` | explicit-intent | existing code/config/evidence | bootstrap specs, not Task | audit/task |
-| `developer` | explicit-implementation-intent | Task and relevant specs | code, Task progress, plans | compliance/review |
-| `quick-dev` | model-auto | relevant specs | bounded code and Task entry | compliance/review |
-| `bug-fix` | both | bug log, relevant code/specs | approved fix, prevention, confirmed bug log | compliance/review |
-| `spec-compliance` | orchestrated | code and applicable specs | report; approved fixes | code-review |
-| `code-review` | both | diff/code, rules, architecture, applicable contracts | report; approved fixes | phase completion |
-| `spec-audit` | both | spec pairs or framework catalog | report; explicitly requested corrections | owning skills |
-| `release-readiness` | both | existing quality/release evidence | report only | release owner |
-| `help` | both | project status/config/catalog | routing report | selected skill |
-| `meet` | both | agenda-relevant evidence | one-round discussion report | owning skills |
+| Skill                     | Invocation                     | Reads                                                | Writes / Output                             | Primary Handoff           |
+| ------------------------- | ------------------------------ | ---------------------------------------------------- | ------------------------------------------- | ------------------------- |
+| `brainstorm-prd`          | explicit-intent                | scope/config, user discovery                         | `PRD.md`                                    | `brainstorm-architecture` |
+| `brainstorm-architecture` | explicit-intent                | PRD                                                  | `architecture.md`                           | schema/API/style/rules    |
+| `brainstorm-schema`       | explicit-intent                | PRD, architecture                                    | `schema.md`                                 | `brainstorm-api`          |
+| `brainstorm-api`          | explicit-intent                | PRD, architecture, schema when applicable            | `api.md`                                    | style/rules/task          |
+| `brainstorm-styleguide`   | explicit-intent                | PRD, architecture                                    | `StyleGuide.md`                             | rules/task                |
+| `brainstorm-rules`        | explicit-intent                | architecture and applicable domain specs             | `rules.md`                                  | `brainstorm-task`         |
+| `brainstorm-task`         | both                           | applicable specs                                     | `Task.md`                                   | `developer`               |
+| `add-feature`             | explicit-intent                | all existing specs                                   | approved spec deltas; delegates Task        | `developer`               |
+| `spec-init`               | explicit-intent                | existing code/config/evidence                        | bootstrap specs, not Task                   | audit/task                |
+| `developer`               | explicit-implementation-intent | Task and relevant specs                              | code, Task progress, plans                  | compliance/review         |
+| `quick-dev`               | model-auto                     | relevant specs                                       | bounded code and Task entry                 | compliance/review         |
+| `bug-fix`                 | both                           | bug log, relevant code/specs                         | approved fix, prevention, confirmed bug log | compliance/review         |
+| `spec-compliance`         | orchestrated                   | code and applicable specs                            | report; approved fixes                      | code-review               |
+| `code-review`             | both                           | diff/code, rules, architecture, applicable contracts | report; approved fixes                      | phase completion          |
+| `spec-audit`              | both                           | spec pairs or framework catalog                      | report; explicitly requested corrections    | owning skills             |
+| `release-readiness`       | both                           | existing quality/release evidence                    | report only                                 | release owner             |
+| `help`                    | both                           | project status/config/catalog                        | routing report                              | selected skill            |
+| `meet`                    | both                           | agenda-relevant evidence                             | one-round discussion report                 | owning skills             |
 
 Framework invariants:
 

package/.agents/skills/_shared/scripts/validate-skills.py

@@ -6,7 +6,6 @@ import re
 import sys
 from pathlib import Path
 
-
 SKILLS_DIR = Path(__file__).resolve().parents[2]
 ALLOWED_FRONTMATTER = {
     "name",
@@ -46,12 +45,14 @@ def parse_frontmatter(path: Path, text: str) -> tuple[dict[str, object], list[st
             continue
         if line.startswith("  "):
             if current_map != "metadata" or ":" not in line:
-                issues.append(f"{path}:{line_number}: unsupported nested frontmatter value")
+                issues.append(
+                    f"{path}:{line_number}: unsupported nested frontmatter value"
+                )
                 continue
             key, value = line.strip().split(":", 1)
             metadata = data.setdefault("metadata", {})
             assert isinstance(metadata, dict)
-            metadata[key] = value.strip().strip('"\'')
+            metadata[key] = value.strip().strip("\"'")
             continue
         if ":" not in line:
             issues.append(f"{path}:{line_number}: invalid frontmatter line")
@@ -62,7 +63,7 @@ def parse_frontmatter(path: Path, text: str) -> tuple[dict[str, object], list[st
             issues.append(f"{path}:{line_number}: duplicate frontmatter key {key}")
         value = value.strip()
         if value:
-            data[key] = value.strip('"\'')
+            data[key] = value.strip("\"'")
             current_map = None
         else:
             data[key] = {}
@@ -93,20 +94,31 @@ def check_skill_file(path: Path) -> list[str]:
     if frontmatter:
         unknown = sorted(set(frontmatter) - ALLOWED_FRONTMATTER)
         if unknown:
-            issues.append(f"{path}: unsupported frontmatter fields: {', '.join(unknown)}")
+            issues.append(
+                f"{path}: unsupported frontmatter fields: {', '.join(unknown)}"
+            )
 
         name = frontmatter.get("name")
         description = frontmatter.get("description")
         if not isinstance(name, str) or not NAME_RE.fullmatch(name) or len(name) > 64:
             issues.append(f"{path}: invalid skill name {name!r}")
         elif name != path.parent.name:
-            issues.append(f"{path}: name {name!r} does not match folder {path.parent.name!r}")
-        if not isinstance(description, str) or not description or len(description) > 1024:
+            issues.append(
+                f"{path}: name {name!r} does not match folder {path.parent.name!r}"
+            )
+        if (
+            not isinstance(description, str)
+            or not description
+            or len(description) > 1024
+        ):
             issues.append(f"{path}: description must contain 1-1024 characters")
         metadata = frontmatter.get("metadata")
         if metadata is not None and (
             not isinstance(metadata, dict)
-            or any(not isinstance(key, str) or not isinstance(value, str) for key, value in metadata.items())
+            or any(
+                not isinstance(key, str) or not isinstance(value, str)
+                for key, value in metadata.items()
+            )
         ):
             issues.append(f"{path}: metadata must be a string-to-string map")
         compatibility = frontmatter.get("compatibility")
@@ -121,14 +133,24 @@ def check_skill_file(path: Path) -> list[str]:
     if "<SECURITY_REVIEW>" in text:
         issues.append(f"{path}: <SECURITY_REVIEW> placeholder was not replaced")
 
-    if re.search(r"^```markdown\s*$", text, re.MULTILINE) and re.search(
-        r"^```(?:json|text|typescript|bash)\s*$", text, re.MULTILINE
-    ):
-        issues.append(
-            f"{path}: possible broken nested fence; check and use 4 backticks for the outer template"
-        )
+    # Check for actual unclosed markdown fences containing inner fences
+    # If a ```markdown block is opened, ensure any nested ``` blocks use 4 backticks ```` or are properly closed
+    if re.search(r"^```markdown\s*$", text, re.MULTILINE):
+        # Scan if there's an inner unescaped fence before closing ```
+        parts = text.split("```markdown")
+        for part in parts[1:]:
+            inside = part.split("\n```\n")[0] if "\n```\n" in part else part
+            if re.search(
+                r"^```(?:json|text|typescript|bash)\s*$", inside, re.MULTILINE
+            ):
+                issues.append(
+                    f"{path}: possible broken nested fence inside ```markdown block; check and use 4 backticks for the outer template"
+                )
 
-    if "[GATE — Fix mode: report-first]" in text and "Approval Resume Protocol" not in text:
+    if (
+        "[GATE — Fix mode: report-first]" in text
+        or "[GATE — Mode: report-first]" in text
+    ) and "Approval Resume Protocol" not in text:
         issues.append(f"{path}: report-first gate has no approval resume protocol")
 
     issues.extend(check_local_links(path, text))

package/.agents/skills/add-feature/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.
+
 At startup:
 
 1. Read `../_shared/references/language-config.md`.
@@ -31,6 +33,7 @@ Operate as `@Galbi` (Project Manager). Use the shared persona profile in `../_sh
 You are a **Product Engineer** adding features to a running project. Do not start from scratch. Read the current specs, understand the context, then update only the affected areas. Every impacted spec is updated; none are skipped.
 
 **Workflow:**
+
 - Read all existing specs first
 - Identify the impact on each document
 - Update ALL impacted specs (required)
@@ -59,13 +62,14 @@ If the user gives a free-form description, extract the relevant information and
 ## Step 1: Read All Existing Specs
 
 Read every existing file in `project-context/`:
+
 - `PRD.md`
 - `architecture.md`
 - `schema.md`
 - `api.md`
 - `rules.md`
 - `StyleGuide.md`
-- `Task.md` *(if it exists; otherwise it will be created by brainstorm-task)*
+- `Task.md` _(if it exists; otherwise it will be created by brainstorm-task)_
 
 Read everything that exists. Skip nothing. Note the ID patterns in use (`FEAT-*`, `BR-*`, `DATA-*`, `API-*`, etc.).
 
@@ -114,15 +118,17 @@ For each **IMPACTED** document, update it in this order:
 4. `api.md` — add endpoints
 5. `StyleGuide.md` — add components/styles
 6. `rules.md` — add conventions if needed
-7. `project-context/plans/` — if a plan file exists for the affected phase (for example `plans/phase-2-checkout.md`), update it to reflect the new scope. Add a section: `## Feature Addition: [feature name]` with a short description of the approach change. Do not overwrite existing plan content.
+7. `project-context/plans/` — if a plan file exists for the affected phase (for example `project-context/plans/phase-2-checkout.md`), update it to reflect the new scope. Add a section: `## Feature Addition: [feature name]` with a short description of the approach change. Do not overwrite existing plan content.
+
+### Update Principles
 
-### Update Principles:
 - **Preserve unrelated content and IDs** — make the smallest targeted edit needed to keep each affected document internally consistent; update an existing statement when the approved feature changes it
 - **Match the existing style** — follow the current document format and tone
 - **Make additions clear** — place them logically; no special tags are needed
 - **Preserve old IDs** — assign new IDs for new items using the existing pattern
 
 After each update:
+
 ```
 ✅ PRD.md updated
    Section: [heading]
@@ -137,12 +143,14 @@ After each update:
 Call `brainstorm-task` to add a phase and tasks to `Task.md`.
 
 **Do not create tasks manually.** The `brainstorm-task` skill:
+
 - Performs deep analysis of the updated specs
 - Ensures task dependencies are ordered correctly
 - Creates testable acceptance criteria
 - Preserves consistency with existing phases
 
 Provide context:
+
 - If `Task.md` exists: "Add a new phase for this feature (do not rewrite everything)"
 - If `Task.md` does not exist: "Create Task.md from scratch using all specs"