refactor: moved plugin to docs dir

Author: bgagent

README.md

@@ -78,12 +78,12 @@ This repository ships a [Claude Code plugin](https://docs.anthropic.com/en/docs/
 ```bash
 git clone https://github.com/aws-samples/sample-autonomous-cloud-coding-agents.git
 cd sample-autonomous-cloud-coding-agents
-claude --plugin-dir abca-plugin
+claude --plugin-dir docs/abca-plugin
 ```
 
-The `--plugin-dir` flag tells Claude Code to load the local plugin from the `abca-plugin/` directory. The plugin's skills, commands, agents, and hooks will be available immediately.
+The `--plugin-dir` flag tells Claude Code to load the local plugin from the `docs/abca-plugin/` directory. The plugin's skills, commands, agents, and hooks will be available immediately.
 
-> **Tip:** If you use Claude Code via VS Code or JetBrains, you can add `--plugin-dir abca-plugin` to the extension's CLI arguments setting.
+> **Tip:** If you use Claude Code via VS Code or JetBrains, you can add `--plugin-dir docs/abca-plugin` to the extension's CLI arguments setting.
 
 #### What the plugin provides
 
@@ -106,16 +106,12 @@ The `--plugin-dir` flag tells Claude Code to load the local plugin from the `abc
 | `cdk-expert` | CDK architecture, construct design, handler implementation, stack modifications |
 | `agent-debugger` | Task failure investigation, CloudWatch log analysis, agent runtime debugging |
 
-**Hook** (runs automatically):
-
-A `SessionStart` hook injects ABCA project context (key directories, commands, conventions) into every Claude Code session.
-
 #### Local plugin development
 
 If you're modifying the plugin itself, here's the file layout:
 
 ```
-abca-plugin/
+docs/abca-plugin/
   plugin.json                    # Plugin manifest (name, version, description)
   skills/
     setup/SKILL.md               # First-time setup workflow
@@ -128,17 +124,14 @@ abca-plugin/
   agents/
     cdk-expert.md                # CDK infrastructure specialist
     agent-debugger.md            # Task failure debugger
-  hooks/
-    hooks.json                   # SessionStart hook configuration
 ```
 
 **Key conventions:**
-- All plugin components live inside `abca-plugin/` alongside the manifest
+- The plugin lives under `docs/` to keep documentation and plugin content colocated
 - Skills live in subdirectories with a `SKILL.md` file (not flat `.md` files)
 - Agents are flat `.md` files with YAML frontmatter
-- Hooks use JSON configuration in `hooks/hooks.json`
 
-**After editing plugin files**, restart Claude Code with `claude --plugin-dir abca-plugin` to pick up changes.
+**After editing plugin files**, restart Claude Code with `claude --plugin-dir docs/abca-plugin` to pick up changes.
 
 ### Manual installation and deployment
 

abca-plugin/README.md docs/abca-plugin/README.mdabca-plugin/README.md renamed to docs/abca-plugin/README.md

@@ -5,14 +5,14 @@ A Claude Code plugin that provides guided workflows for setting up, deploying, o
 ## Installation
 
 ```bash
-claude --plugin-dir abca-plugin
+claude --plugin-dir docs/abca-plugin
 ```
 
 Or add to your project's `.claude/settings.json`:
 
 ```json
 {
-  "plugins": ["./abca-plugin"]
+  "plugins": ["./docs/abca-plugin"]
 }
 ```
 
@@ -37,20 +37,14 @@ Or add to your project's `.claude/settings.json`:
 | `cdk-expert` | Sonnet | AWS CDK infrastructure expert for construct design, handler implementation, and stack modifications |
 | `agent-debugger` | Sonnet | Read-only debugging specialist for task failures, preflight errors, and CloudWatch log analysis |
 
-### Hooks
-
-- **SessionStart** — Injects ABCA project context (directory structure, key commands, task types, available skills/agents) into every Claude Code session.
-
 ## Plugin Structure
 
 ```
-abca-plugin/
+docs/abca-plugin/
   plugin.json              # Plugin manifest
   agents/
     cdk-expert.md          # CDK infrastructure agent
     agent-debugger.md      # Runtime debugging agent
-  hooks/
-    hooks.json             # SessionStart context injection
   skills/
     setup/SKILL.md         # First-time setup workflow
     deploy/SKILL.md        # CDK deployment management
@@ -63,21 +57,20 @@ abca-plugin/
 
 ## Testing
 
-This plugin is markdown and configuration only (no executable code), so traditional unit tests don't apply. Instead, a **4-layer validation strategy** verifies correctness:
+This plugin is markdown and configuration only (no executable code), so traditional unit tests don't apply. Instead, a **3-layer validation strategy** verifies correctness:
 
 | Layer | What it checks |
 |-------|---------------|
 | **1. Structural** | `plugin.json` fields, file discovery, JSON/YAML validity, no orphaned files |
 | **2. Agent Config** | Frontmatter fields (`model`, `tools`, `description`), valid tool names, file path accuracy, capability alignment with examples |
 | **3. Content Integrity** | All repo paths exist, all `mise run` commands are valid tasks, all `bgagent` CLI flags match actual help output, skill cross-references resolve, AWS CLI syntax is correct |
-| **4. Hooks** | `hooks.json` structure, supported event names, skills/agents listed in hook content all exist, no sensitive data |
 
 ### Running the tests
 
 From the repo root with Claude Code:
 
 ```
-claude --plugin-dir abca-plugin
+claude --plugin-dir docs/abca-plugin
 ```
 
 Then ask Claude to validate the plugin:
@@ -91,8 +84,7 @@ Or run the checks manually:
 
 ```bash
 # Layer 1: Structural — valid JSON
-python3 -c "import json; json.load(open('abca-plugin/plugin.json')); print('plugin.json OK')"
-python3 -c "import json; json.load(open('abca-plugin/hooks/hooks.json')); print('hooks.json OK')"
+python3 -c "import json; json.load(open('docs/abca-plugin/plugin.json')); print('plugin.json OK')"
 
 # Layer 3: Content — mise tasks exist
 MISE_EXPERIMENTAL=1 mise tasks --all 2>/dev/null | grep -E '(build|install|compile|test|deploy|destroy|diff|synth|bootstrap)'
@@ -105,7 +97,6 @@ node cli/lib/bin/bgagent.js submit --help && node cli/lib/bin/bgagent.js list --
 
 To modify the plugin:
 
-1. Edit the relevant `.md` file under `skills/`, `agents/`, or `hooks/`
+1. Edit the relevant `.md` file under `skills/` or `agents/`
 2. Re-validate using the testing strategy above
 3. Ensure any new file paths or commands you reference actually exist in the repo
-4. Keep the `SessionStart` hook prompt in sync if you add/remove/rename skills or agents