@codemcp/ade 0.2.6 → 0.4.0

package/.agentskills/skills/conventional-commits/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: conventional-commits
+description: Conventional Commits specification for structured commit messages
+---
+
+# Conventional Commits
+
+## Format
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+## Types
+
+- `feat`: A new feature (correlates with MINOR in SemVer)
+- `fix`: A bug fix (correlates with PATCH in SemVer)
+- `docs`: Documentation only changes
+- `style`: Changes that do not affect the meaning of the code
+- `refactor`: A code change that neither fixes a bug nor adds a feature
+- `perf`: A code change that improves performance
+- `test`: Adding missing tests or correcting existing tests
+- `chore`: Changes to the build process or auxiliary tools
+
+## Rules
+
+- Subject line must not exceed 72 characters
+- Use imperative mood in the subject line ("add" not "added")
+- Do not end the subject line with a period
+- Separate subject from body with a blank line
+- Use the body to explain what and why, not how
+- `BREAKING CHANGE:` footer or `!` after type/scope for breaking changes

package/.beads/issues.jsonl

@@ -50,3 +50,13 @@
 {"id":"ade-3.3","title":"Fix","description":"Implement the solution based on your analysis:  - If  exists: Follow the design from it - Otherwise: Elaborate design options and present them to the user  Before implementing, assess the approach: - How critical is this system? What is the blast radius if the fix causes issues? - Should this be a minimal fix or a more comprehensive solution?  Make targeted changes that address the root cause without introducing new issues. Be careful to maintain existing functionality while fixing the bug.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T16:29:10.265074+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T16:29:10.265074+01:00","dependencies":[{"issue_id":"ade-3.3","depends_on_id":"ade-3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-3.3","depends_on_id":"ade-3.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-3.4","title":"Verify","description":"Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced. Run existing tests, create new ones if needed, and verify the solution is robust.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T16:29:10.449967+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T16:29:10.449967+01:00","dependencies":[{"issue_id":"ade-3.4","depends_on_id":"ade-3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-3.4","depends_on_id":"ade-3.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-3.5","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review.  **STEP 1: Code Cleanup** Systematically clean up development artifacts: - Remove all temporary debug output statements used during bug investigation (console logging, print statements, debug output functions) - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred - Remove completed TODOs and convert remaining ones to proper issue tracking if needed - Remove temporary debugging code, test code blocks, and commented-out code - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect the bug fix: - If  exists, update it if design details were refined or changed during the fix - Compare documentation against the actual bug fix implementation - Update only the documentation sections that have functional changes - Remove references to investigation iterations, progress notes, and temporary decisions - Ensure documentation describes the final fixed state, not the debugging process - Ask the user to review document updates  **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure bug fix is ready for production - Update task progress and mark completed work as you finalize the bug fix","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T16:29:10.642935+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T16:29:10.642935+01:00","dependencies":[{"issue_id":"ade-3.5","depends_on_id":"ade-3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-3.5","depends_on_id":"ade-3.4","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-4","title":"ade: bugfix (development-plan-fix-no-git.md)","description":"Responsible vibe engineering session using bugfix workflow for ade","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T10:33:06.662828+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T10:33:06.662828+01:00"}
+{"id":"ade-4.1","title":"Reproduce","description":"Gather specific information to reliably reproduce the reported bug: - What are the exact OS, browser/runtime versions, and hardware specs? - What is the precise sequence of actions that trigger the bug? - What error messages, logs, or stack traces are available? - Does this happen every time or intermittently? - How many users are affected and what is the business impact?  Create test cases that demonstrate the problem. Document your findings and create tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T10:33:06.80022+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T10:33:06.80022+01:00","dependencies":[{"issue_id":"ade-4.1","depends_on_id":"ade-4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-4.2","title":"Analyze","description":"Examine the code paths involved in the bug, identify the root cause, and understand why the issue occurs. Use debugging tools, add logging, and trace through the problematic code. Document your analysis and create tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T10:33:06.939399+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T10:33:06.939399+01:00","dependencies":[{"issue_id":"ade-4.2","depends_on_id":"ade-4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-4.2","depends_on_id":"ade-4.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-4.3","title":"Fix","description":"Implement the solution based on your analysis:  - If  exists: Follow the design from it - Otherwise: Elaborate design options and present them to the user  Before implementing, assess the approach: - How critical is this system? What is the blast radius if the fix causes issues? - Should this be a minimal fix or a more comprehensive solution?  Make targeted changes that address the root cause without introducing new issues. Be careful to maintain existing functionality while fixing the bug.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T10:33:07.076548+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T10:33:07.076548+01:00","dependencies":[{"issue_id":"ade-4.3","depends_on_id":"ade-4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-4.3","depends_on_id":"ade-4.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-4.4","title":"Verify","description":"Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced. Run existing tests, create new ones if needed, and verify the solution is robust.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T10:33:07.222264+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T10:33:07.222264+01:00","dependencies":[{"issue_id":"ade-4.4","depends_on_id":"ade-4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-4.4","depends_on_id":"ade-4.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-4.5","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review.  **STEP 1: Code Cleanup** Systematically clean up development artifacts: - Remove all temporary debug output statements used during bug investigation (console logging, print statements, debug output functions) - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred - Remove completed TODOs and convert remaining ones to proper issue tracking if needed - Remove temporary debugging code, test code blocks, and commented-out code - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect the bug fix: - If  exists, update it if design details were refined or changed during the fix - Compare documentation against the actual bug fix implementation - Update only the documentation sections that have functional changes - Remove references to investigation iterations, progress notes, and temporary decisions - Ensure documentation describes the final fixed state, not the debugging process - Ask the user to review document updates  **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure bug fix is ready for production - Update task progress and mark completed work as you finalize the bug fix","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T10:33:07.356694+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T10:33:07.356694+01:00","dependencies":[{"issue_id":"ade-4.5","depends_on_id":"ade-4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-4.5","depends_on_id":"ade-4.4","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-5","title":"ade: minor (development-plan-better-in-cli-explanation.md)","description":"Responsible vibe engineering session using minor workflow for ade","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.313751+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.313751+01:00"}
+{"id":"ade-5.1","title":"Explore","description":"Understand the problem, analyze existing patterns, and design your approach. Consider the scope and impact of the change. **STEP 1: Analyze Requirements** - If  exists: Use it to understand the required changes - Otherwise: Document requirements in your task management system **STEP 2: Review Design Approach** - If  exists: Respect the design approach documented in  - Otherwise: Design your approach based on the problem analysis **STEP 3: Document Decisions** - Document your analysis and design decisions - Create tasks to guide implementation - Focus on analysis and design only - do not write any code yet","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.459272+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.459272+01:00","dependencies":[{"issue_id":"ade-5.1","depends_on_id":"ade-5","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-5.2","title":"Implement","description":"Write clean, focused code for the minor enhancement, test your changes, and prepare for commit. **STEP 1: Review Design and Requirements** - If  exists: Follow your design from  - Otherwise: Elaborate design options and present them to the user - If  exists: Ensure the relevant requirements from  are met - Otherwise: Ensure existing requirements are met based on your task context **STEP 2: Implement Changes** - Write clean, focused code for the minor enhancement - Test your changes to ensure they work correctly and don't break existing functionality **STEP 3: Prepare for Finalization** - Update task progress as needed - Prepare documentation and commit when ready","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.597501+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.597501+01:00","dependencies":[{"issue_id":"ade-5.2","depends_on_id":"ade-5","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-5.2","depends_on_id":"ade-5.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-5.3","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review. **STEP 1: Code Cleanup** Systematically clean up development artifacts: - **Remove Debug Output**: Search for and remove all temporary debug output statements used during development.   Look for language-specific debug output methods (console logging, print statements, debug output functions).   Remove any debugging statements that were added for development purposes.  - **Review TODO/FIXME Comments**:   - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred   - Remove completed TODOs   - Convert remaining TODOs to proper issue tracking if needed  - **Remove Debugging Code Blocks**:   - Remove temporary debugging code, test code blocks, and commented-out code   - Clean up any experimental code that's no longer needed   - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect final implementation: - **Update Long-Term Memory Documents**: Based on what was actually implemented:   - If  exists: Update  if requirements changed during development   - If  exists: Update  if design details were refined or changed - **Compare Against Implementation**: Review documentation against actual implemented functionality - **Update Changed Sections**: Only modify documentation sections that have functional changes - **Remove Development Progress**: Remove references to development iterations, progress notes, and temporary decisions - **Focus on Final State**: Ensure documentation describes the final implemented state, not the development process - **Ask User to Review Document Updates** **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure minor enhancement is ready for delivery - Update task progress and mark completed work as you finalize the minor enhancement","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.733496+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.733496+01:00","dependencies":[{"issue_id":"ade-5.3","depends_on_id":"ade-5","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-5.3","depends_on_id":"ade-5.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}

package/.beads/last-touched

@@ -1 +1 @@
-ade-3.5
+ade-5.3

package/.kiro/agents/ade.json

@@ -14,7 +14,14 @@
       "autoApprove": ["*"]
     }
   },
-  "tools": ["read", "write", "spec", "@workflows/*", "@agentskills/*", "shell"],
-  "allowedTools": ["read", "write", "spec", "@workflows/*", "@agentskills/*"],
+  "tools": ["read", "write", "shell", "spec", "@workflows/*", "@agentskills/*"],
+  "allowedTools": [
+    "read",
+    "write",
+    "shell",
+    "spec",
+    "@workflows/*",
+    "@agentskills/*"
+  ],
   "useLegacyMcpJson": true
 }

package/.opencode/agents/ade.md

@@ -7,25 +7,25 @@ permission:
     "*.env": "deny"
     "*.env.*": "deny"
     "*.env.example": "allow"
-  edit: "allow"
+  skill: "deny"
+  todoread: "deny"
+  todowrite: "deny"
+  task: "deny"
+  lsp: "allow"
   glob: "allow"
   grep: "allow"
   list: "allow"
-  lsp: "allow"
-  task: "allow"
-  todoread: "deny"
-  todowrite: "deny"
-  skill: "deny"
+  external_directory: "ask"
+  edit: "allow"
   webfetch: "ask"
   websearch: "ask"
   codesearch: "ask"
   bash:
-    "*": "deny"
+    "*": "ask"
     "grep *": "allow"
     "rg *": "allow"
     "find *": "allow"
     "fd *": "allow"
-    ls: "allow"
     "ls *": "allow"
     "cat *": "allow"
     "head *": "allow"
@@ -60,14 +60,7 @@ permission:
     "yq *": "allow"
     "mkdir *": "allow"
     "touch *": "allow"
-    "cp *": "ask"
-    "mv *": "ask"
-    "ln *": "ask"
-    "npm *": "ask"
-    "node *": "ask"
-    "pip *": "ask"
-    "python *": "ask"
-    "python3 *": "ask"
+    "kill *": "ask"
     "rm *": "deny"
     "rmdir *": "deny"
     "curl *": "deny"
@@ -88,7 +81,6 @@ permission:
     "mkfs *": "deny"
     "mount *": "deny"
     "umount *": "deny"
-    "kill *": "deny"
     "killall *": "deny"
     "pkill *": "deny"
     "nc *": "deny"
@@ -107,7 +99,6 @@ permission:
     "useradd *": "deny"
     "userdel *": "deny"
     "iptables *": "deny"
-  external_directory: "deny"
   doom_loop: "deny"
 ---
 

package/.vibe/beads-state-ade-better-in-cli-explanation-b8jcv3.json

@@ -0,0 +1,24 @@
+{
+  "conversationId": "ade-better-in-cli-explanation-b8jcv3",
+  "projectPath": "/Users/oliverjaegle/projects/privat/codemcp/ade",
+  "epicId": "ade-5",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "ade-5.1"
+    },
+    {
+      "phaseId": "implement",
+      "phaseName": "Implement",
+      "taskId": "ade-5.2"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "ade-5.3"
+    }
+  ],
+  "createdAt": "2026-03-19T10:33:13.963Z",
+  "updatedAt": "2026-03-19T10:33:13.963Z"
+}

package/.vibe/beads-state-ade-fix-no-git-k396xs.json

@@ -0,0 +1,34 @@
+{
+  "conversationId": "ade-fix-no-git-k396xs",
+  "projectPath": "/Users/oliverjaegle/projects/privat/codemcp/ade",
+  "epicId": "ade-4",
+  "phaseTasks": [
+    {
+      "phaseId": "reproduce",
+      "phaseName": "Reproduce",
+      "taskId": "ade-4.1"
+    },
+    {
+      "phaseId": "analyze",
+      "phaseName": "Analyze",
+      "taskId": "ade-4.2"
+    },
+    {
+      "phaseId": "fix",
+      "phaseName": "Fix",
+      "taskId": "ade-4.3"
+    },
+    {
+      "phaseId": "verify",
+      "phaseName": "Verify",
+      "taskId": "ade-4.4"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "ade-4.5"
+    }
+  ],
+  "createdAt": "2026-03-19T09:33:07.866Z",
+  "updatedAt": "2026-03-19T09:33:07.866Z"
+}

package/.vibe/development-plan-better-in-cli-explanation.md

@@ -0,0 +1,64 @@
+# Development Plan: ade (better-in-cli-explanation branch)
+
+*Generated on 2026-03-19 by Vibe Feature MCP*
+*Workflow: [minor](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/minor)*
+
+## Goal
+Improve user guidance in the ADE CLI — add contextual introductory text to help users understand what ADE is and what each setup facet (Process, Architecture, Practices, Autonomy, Backpressure, Harnesses, Docsets) means before they make a selection.
+
+## Explore
+<!-- beads-phase-id: ade-5.1 -->
+### Tasks
+- [x] Read and understand current CLI structure (index.ts, setup.ts, install.ts)
+- [x] Read all facet definitions (process, architecture, practices, autonomy, backpressure)
+- [x] Identify all prompts where contextual guidance is missing
+
+### Findings
+- The setup command starts with `clack.intro("ade setup")` — no explanation of what ADE is or what the wizard will do
+- Facet prompts show only `facet.label` as the message — no educational context about what the facet means
+- The harness prompt says "which coding agents should receive config?" — helpful but no context on what harnesses are
+- The docset prompt says "deselect any you don't need" — no explanation of what docsets are used for
+- The skill install confirm says only "Install N skill(s) now?" — no context on what skills are
+- `index.ts` help text is minimal — no explanation of ADE's purpose
+
+### Phase Entrance Criteria for Implement:
+- [x] All touchpoints where user guidance is missing have been identified
+- [x] Content approach is clear (what to say at each step)
+- [x] No ambiguity about scope (we're adding text/hints, not redesigning prompts)
+
+## Implement
+<!-- beads-phase-id: ade-5.2 -->
+
+### Phase Entrance Criteria:
+- [x] Explore phase findings are complete
+- [x] All identified touchpoints for improvement are listed
+- [x] Scope is clearly defined: text additions only, no structural changes
+
+### Tasks
+*Tasks managed via `bd` CLI*
+
+## Finalize
+<!-- beads-phase-id: ade-5.3 -->
+
+### Phase Entrance Criteria:
+- [x] All identified touchpoints have been addressed with guidance text
+- [x] Code compiles without errors
+- [x] Changes look correct and consistent in tone
+
+### Tasks
+- [ ] Squash WIP commits: `git reset --soft <first commit of this branch>`. Then, create a conventional commit. In the message, first summarize the intentions and key decisions from the development plan. Then, add a brief summary of the key changes and their side effects and dependencies
+
+*Tasks managed via `bd` CLI*
+
+## Key Decisions
+- Used `clack.note()` for the ADE intro (boxed, titled) to make it stand out as orientation content vs. action prompts
+- Used `clack.log.info()` before each facet/section prompt — lightweight, doesn't interrupt the flow, provides context without being intrusive
+- Facet descriptions from the catalog data model are reused directly (they were already well-written) rather than duplicated elsewhere
+- Harness guidance explicitly calls out the 'universal' option since it's the most common default and its purpose isn't obvious from the name alone
+- Skill install context placed immediately before the confirm prompt so it reads naturally in sequence
+
+## Notes
+*Additional context and observations*
+
+---
+*This plan is maintained by the LLM and uses beads CLI for task management. Tool responses provide guidance on which bd commands to use for task management.*

package/.vibe/development-plan-fix-no-git.md

@@ -0,0 +1,76 @@
+# Development Plan: ade (fix-no-git branch)
+
+*Generated on 2026-03-19 by Vibe Feature MCP*
+*Workflow: [bugfix](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/bugfix)*
+
+## Goal
+Fix `writeGitHooks` crashing with ENOENT when run in a non-git directory. Instead of throwing, it should detect the absence of `.git` and emit a warning, then skip gracefully (Option B).
+
+## Reproduce
+<!-- beads-phase-id: ade-4.1 -->
+### Bug Description
+When `ade setup` is run in a non-git directory and pre-commit hooks are configured, `writeGitHooks` tries to open `.git/hooks/pre-commit` for writing. Since `.git` doesn't exist, Node throws `ENOENT` and the whole process crashes.
+
+### Error
+```
+Error: ENOENT: no such file or directory, open '/private/tmp/manual-test/.git/hooks/pre-commit'
+```
+
+### Root Cause (already identified via code reading)
+`packages/harnesses/src/util.ts` → `writeGitHooks()` writes directly to `.git/hooks/<phase>` without checking if `.git` exists.
+
+### Tasks
+
+## Analyze
+<!-- beads-phase-id: ade-4.2 -->
+### Phase Entrance Criteria
+- [x] Bug is reproducible and root cause is identified.
+- [x] Affected code location is known (`writeGitHooks` in `packages/harnesses/src/util.ts`).
+
+### Analysis
+- `writeGitHooks` is a shared utility called by every harness writer (universal, cursor, copilot, cline, claude-code, roo-code, opencode, kiro, windsurf).
+- The fix belongs in `writeGitHooks` itself — one place, all callers benefit.
+- Chosen approach: **Option B** — check for `.git` existence; if absent, emit a `clack.log.warn(...)` and return early. This keeps the user informed (backpressure) without crashing.
+- `clack` is already used throughout the codebase; it is available in `util.ts`.
+
+### Tasks
+
+## Fix
+<!-- beads-phase-id: ade-4.3 -->
+### Phase Entrance Criteria
+- [x] Root cause is confirmed to be in `writeGitHooks`.
+- [x] Fix strategy (Option B: warn + skip) is agreed upon.
+
+### Tasks
+- [ ] In `writeGitHooks`: use `fs/promises.access` to check for `.git` directory existence before writing hooks.
+- [ ] If `.git` is absent, call `clack.log.warn(...)` with a clear message and return.
+- [ ] Also ensure `.git/hooks` directory is created if `.git` exists but `hooks` subdir is missing (use `mkdir` with `recursive: true`).
+- [ ] Add / update unit tests in `install.spec.ts` or `util.spec.ts` to cover the non-git-repo case.
+
+## Verify
+<!-- beads-phase-id: ade-4.4 -->
+### Phase Entrance Criteria
+- [ ] `writeGitHooks` checks for `.git` existence and warns instead of crashing.
+- [ ] `.git/hooks` dir is created when `.git` exists but `hooks` subdir is missing.
+- [ ] Unit tests cover the new behavior.
+
+### Tasks
+- [ ] Run existing test suite and confirm no regressions.
+- [ ] Manually verify the warning message is shown when run outside a git repo.
+
+## Finalize
+<!-- beads-phase-id: ade-4.5 -->
+### Phase Entrance Criteria
+- [ ] All tests pass.
+- [ ] Warning behavior verified.
+
+### Tasks
+- [ ] Squash WIP commits: `git reset --soft <first commit of this branch>`. Then, create a conventional commit. In the message, first summarize the intentions and key decisions from the development plan. Then, add a brief summary of the key changes and their side effects and dependencies.
+
+## Key Decisions
+- **Option B (warn + skip)** chosen over silent skip so users receive feedback that hooks were not installed — this preserves backpressure (user knows something was skipped).
+- Fix is centralised in `writeGitHooks` utility; no changes needed in individual harness writers.
+
+## Notes
+- `clack` import must be added to `util.ts` if not already present.
+- All harness writers already import `writeGitHooks` from `../util.js` — no call-site changes needed.

package/AGENTS.md

@@ -0,0 +1,27 @@
+# AGENTS
+
+You are an AI assistant that helps users develop software features using the workflows server.
+IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
+Each tool call returns a JSON response with an "instructions" field. Follow these instructions immediately after you receive them.
+Use the development plan which you will retrieve via whats_next() to record important insights and decisions as per the structure of the plan.
+Do not use your own task management tools.
+
+## Autonomy
+
+Universal harness limitation: `AGENTS.md` + `.mcp.json` provide documentation and server registration only; there is no enforceable harness-level permission schema here.
+
+Treat this autonomy profile as documentation-only guidance for built-in/basic operations.
+
+Profile: `sensible-defaults`
+
+Built-in/basic capability guidance:
+
+- `read`: allow
+- `edit_write`: allow
+- `search_list`: allow
+- `bash_safe`: allow
+- `bash_unsafe`: ask
+- `web`: ask
+- `task_agent`: allow
+
+MCP permissions are not re-modeled by autonomy here; any MCP approvals must come from provisioning-aware consuming harnesses rather than the Universal writer.

package/config.lock.yaml

@@ -1,9 +1,10 @@
 version: 1
-generated_at: 2026-03-18T11:52:51.718Z
+generated_at: 2026-03-19T09:28:46.177Z
 choices:
   process: codemcp-workflows
   practices:
     - adr-nygard
+    - conventional-commits
   autonomy: sensible-defaults
 harnesses:
   - universal
@@ -104,15 +105,38 @@ logical_config:
 
         - Title should be a short noun phrase (e.g. "Use PostgreSQL for
         persistence")
+    - name: conventional-commits
+      description: Conventional Commits specification for structured commit messages
+      body: |-
+        # Conventional Commits
+
+        ## Format
+        ```
+        <type>[optional scope]: <description>
+
+        [optional body]
+
+        [optional footer(s)]
+        ```
+
+        ## Types
+        - `feat`: A new feature (correlates with MINOR in SemVer)
+        - `fix`: A bug fix (correlates with PATCH in SemVer)
+        - `docs`: Documentation only changes
+        - `style`: Changes that do not affect the meaning of the code
+        - `refactor`: A code change that neither fixes a bug nor adds a feature
+        - `perf`: A code change that improves performance
+        - `test`: Adding missing tests or correcting existing tests
+        - `chore`: Changes to the build process or auxiliary tools
+
+        ## Rules
+        - Subject line must not exceed 72 characters
+        - Use imperative mood in the subject line ("add" not "added")
+        - Do not end the subject line with a period
+        - Separate subject from body with a blank line
+        - Use the body to explain what and why, not how
+        - `BREAKING CHANGE:` footer or `!` after type/scope for breaking changes
   git_hooks: []
   setup_notes: []
   permission_policy:
     profile: sensible-defaults
-    capabilities:
-      read: allow
-      edit_write: allow
-      search_list: allow
-      bash_safe: allow
-      bash_unsafe: ask
-      web: ask
-      task_agent: allow

package/config.yaml

@@ -2,7 +2,10 @@ choices:
   process: codemcp-workflows
   practices:
     - adr-nygard
+    - conventional-commits
   autonomy: sensible-defaults
+excluded_docsets:
+  - conventional-commits-spec
 harnesses:
   - universal
   - opencode

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/ade",
-  "version": "0.2.6",
+  "version": "0.4.0",
   "description": "ADE CLI — Agentic Development Environment setup and configuration tool",
   "license": "MIT",
   "keywords": [