@relipa/ai-flow-kit 0.0.4-beta.2 → 0.0.4

package/custom/templates/tools/claude.md

@@ -0,0 +1,13 @@
+# Claude AI System Instructions
+
+You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
+
+> **Important:** Always read `.aiflow/context/current.json` to load ticket context and check the `plan/` directory for existing progress before starting any task.
+
+If Gate 1 does not auto-start, wait for the developer to type **"start"**, **"Gate 1"** or **"Analyze ticket"**.
+
+## Interaction Rules:
+
+- **COLLABORATIVE SKILLS:** When a skill (like `brainstorming`) says to "ask one question at a time", you MUST stop and wait for the developer's reply before proceeding.
+- **NEVER BATCH QUESTIONS:** Only ask one question per message.
+- **WAIT FOR APPROVAL:** Do not move to the next Gate until you receive "APPROVED".

package/custom/templates/tools/copilot.md

@@ -1,8 +1,12 @@
-# GitHub Copilot Custom Instructions
-
-You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
-
-> [!IMPORTANT]
-> Always check for context in `.claude/context/current.json` and progress in the `plan/` folder before suggesting changes.
-
-If the Gate Workflow hasn't started, wait for the developer to type **"start"** or **"Gate 1"**.
+# GitHub Copilot Custom Instructions
+
+You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
+
+> **Important:** Always check for context in `.aiflow/context/current.json` and progress in the `plan/` folder before suggesting changes.
+
+If the Gate Workflow hasn't started, wait for the developer to type **"start"** or **"Gate 1"**.
+
+## Interaction Rules:
+- **COLLABORATIVE SKILLS:** When a skill (like `brainstorming`) says to "ask one question at a time", you MUST stop and wait for the developer's reply before proceeding.
+- **NEVER BATCH QUESTIONS:** Only ask one question per message.
+- **WAIT FOR APPROVAL:** Do not move to the next Gate until you receive "APPROVED".

package/custom/templates/tools/cursor.md

@@ -1,8 +1,12 @@
-# Cursor AI Project Rules
-
-You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
-
-> [!IMPORTANT]
-> Always check `.claude/context/current.json` and the `plan/` directory before starting any task to understand current context and progress.
-
-If Gate 1 doesn't auto-start, wait for the developer to type **"start"**, **"Gate 1"** or **"Analyze ticket"**.
+# Cursor AI Project Rules
+
+You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
+
+> **Important:** Always check `.aiflow/context/current.json` and the `plan/` directory before starting any task to understand current context and progress.
+
+If Gate 1 doesn't auto-start, wait for the developer to type **"start"**, **"Gate 1"** or **"Analyze ticket"**.
+
+## Interaction Rules:
+- **COLLABORATIVE SKILLS:** When a skill (like `brainstorming`) says to "ask one question at a time", you MUST stop and wait for the developer's reply before proceeding.
+- **NEVER BATCH QUESTIONS:** Only ask one question per message.
+- **WAIT FOR APPROVAL:** Do not move to the next Gate until you receive "APPROVED".

package/custom/templates/tools/gemini.md

@@ -1,8 +1,12 @@
-# Gemini AI System Instructions
-
-You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
-
-> [!IMPORTANT]
-> When starting a session, always read `.claude/context/current.json` to load ticket context and check the `plan/` directory for existing progress.
-
-If no instructions are automatically followed, wait for the developer to type **"start"** or **"Gate 1"** to start the analysis.
+# Gemini AI System Instructions
+
+You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
+
+> **Important:** When starting a session, always read `.aiflow/context/current.json` to load ticket context and check the `plan/` directory for existing progress.
+
+If no instructions are automatically followed, wait for the developer to type **"start"** or **"Gate 1"** to start the analysis.
+
+## Interaction Rules:
+- **COLLABORATIVE SKILLS:** When a skill (like `brainstorming`) says to "ask one question at a time", you MUST stop and wait for the developer's reply before proceeding.
+- **NEVER BATCH QUESTIONS:** Only ask one question per message.
+- **WAIT FOR APPROVAL:** Do not move to the next Gate until you receive "APPROVED".

package/custom/templates/tools/generic.md

@@ -1,12 +1,17 @@
-# AI System Instructions
-
-You are an expert AI assistant. Follow the project's Gate Workflow and Team Rules strictly.
-
-## Context Awareness
-- **Ticket context**: `.claude/context/current.json`
-- **Task progress**: `plan/[ticket-id]/`
-- **Rules**: `.rules/`
-
-Follow the gated workflow and rules defined below.
-
-If Gate 1 does not start automatically, please start it when the developer types **"Gate 1"**.
+# AI System Instructions
+
+You are an expert AI assistant. Follow the project's Gate Workflow and Team Rules strictly.
+
+## Context Awareness
+- **Ticket context**: `.aiflow/context/current.json`
+- **Task progress**: `plan/[ticket-id]/`
+- **Rules**: `.rules/`
+
+Follow the gated workflow and rules defined below.
+
+If Gate 1 does not start automatically, please start it when the developer types **"Gate 1"**.
+
+## Interaction Rules:
+- **COLLABORATIVE SKILLS:** When a skill (like `brainstorming`) says to "ask one question at a time", you MUST stop and wait for the developer's reply before proceeding.
+- **NEVER BATCH QUESTIONS:** Only ask one question per message.
+- **WAIT FOR APPROVAL:** Do not move to the next Gate until you receive "APPROVED".

package/custom/templates/vue-nuxt.md

@@ -1,14 +1,14 @@
-# Vue/Nuxt.js AI System Prompt
-
-You are an expert Vue.js & Nuxt 3 developer. Follow these rules.
-
----
-
-- Use `<script setup lang="ts">` with Composition API exclusively. Do not use the Options API.
-- Use explicit Nuxt auto-imports where appropriate, but maintain clarity on complex utilities.
-- For state management, prefer Pinia or native `useState` bindings in Nuxt.
-- Use `useFetch` or `useAsyncData` for server-side data fetching. Use `$fetch` for client-side API requests outside component initialization.
-- Keep components small and specialized.
-- Adhere to the official Vue Style Guide (Priority A and B).
-
-Ensure code is strictly typed with TypeScript.
+# Vue/Nuxt.js AI System Prompt
+
+You are an expert Vue.js & Nuxt 3 developer. Follow these rules.
+
+---
+
+- Use `<script setup lang="ts">` with Composition API exclusively. Do not use the Options API.
+- Use explicit Nuxt auto-imports where appropriate, but maintain clarity on complex utilities.
+- For state management, prefer Pinia or native `useState` bindings in Nuxt.
+- Use `useFetch` or `useAsyncData` for server-side data fetching. Use `$fetch` for client-side API requests outside component initialization.
+- Keep components small and specialized.
+- Adhere to the official Vue Style Guide (Priority A and B).
+
+Ensure code is strictly typed with TypeScript.

package/{AIFLOW.md → docs/AIFLOW.md}

@@ -83,7 +83,7 @@ claude                           # open Claude → AI auto-starts Gate 1
 
 | Step | Action | Purpose |
 |------|--------|---------|
-| 1 | Load ticket from `.claude/context/current.json` | Get PM's requirements, comments |
+| 1 | Load ticket from `.aiflow/context/current.json` | Get PM's requirements, comments |
 | 2 | Read `CLAUDE.md` + source code | Understand architecture, tech stack, patterns |
 | 3 | Investigate related files & data flow | Identify affected areas, dependencies |
 | 4 | Ask clarifying questions (one at a time) | Ensure full understanding |
@@ -415,7 +415,7 @@ aiflow guide                          # view quickstart guide
 
 ## Multi-AI Environment Setup
 
-One of the core strengths of `ai-flow-kit` is that the **Gate Workflow** is tool-agnostic. Since state is saved in `.claude/context/current.json` and the `plan/` directory, you can switch tools mid-task.
+One of the core strengths of `ai-flow-kit` is that the **Gate Workflow** is tool-agnostic. Since state is saved in `.aiflow/context/current.json` and the `plan/` directory, you can switch tools mid-task.
 
 ### How to Switch Tools
 1. **Analyze (Gate 1)** using Claude Code CLI (great for deep codebase scans).

package/{CHANGELOG.md → docs/CHANGELOG.md}

@@ -7,9 +7,21 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
-## [Unreleased]
+## [0.0.4-beta.5] - 2026-04-21
+
+### Added
+- Created a dedicated `docs/` folder to house all developer-facing documentation.
+- Integrated AI Skill Registry into all tool templates (Claude, Cursor, Gemini, Copilot) for better skill discovery.
+
+### Changed
+- Moved `README.md`, `QUICK_START.md`, `AIFLOW.md`, `CHANGELOG.md`, and `IMPLEMENTATION_SUMMARY.md` into the `docs/` directory.
+- Updated `package.json` to exclude internal-only files (`CONTRIBUTING.md`, `plan.md`) from the NPM package distribution.
+- Updated `scripts/init.js` to source documentation from the new `docs/` location.
+- Updated all internal documentation links to reflect the new directory structure.
+
+---
 
-> Changes that are merged but not yet released.
+## [Unreleased]
 
 ---
 
@@ -64,7 +76,6 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 #### Project Templates
 - `AIFLOW.md` — team workflow reference document
 - `QUICK_START.md` — 5-minute setup guide
-- `CONTRIBUTING.md` — contributor guide
 - `.aiflowrc.json.example` — configuration file reference
 
 ### Architecture Notes

package/{IMPLEMENTATION_SUMMARY.md → docs/IMPLEMENTATION_SUMMARY.md}

@@ -64,7 +64,7 @@ Complete overview of what has been implemented.
 ### Tier 2: Developer Experience (COMPLETED)
 
 #### 5. ✅ Documentation & Onboarding
-- **Files:** `docs/*.md`, `README.md`, `CONTRIBUTING.md`, `QUICK_START.md`
+- **Files:** `docs/*.md`
 - **Documentation Includes:**
   - **README.md** — Package overview, features, usage
   - **QUICK_START.md** — 5-minute getting started
@@ -73,7 +73,6 @@ Complete overview of what has been implemented.
   - **docs/configuration.md** — All configuration options
   - **docs/cli-reference.md** — Complete CLI command reference
   - **docs/troubleshooting.md** — Common issues and solutions
-  - **CONTRIBUTING.md** — How to extend the package
   - **Workflow Guides:**
     - `docs/workflows/bug-fix.md` — Fix production issues
     - `docs/workflows/feature.md` — Build new features
@@ -185,6 +184,23 @@ Complete overview of what has been implemented.
 ai-flow-kit/
 ├── bin/
 │   └── aiflow.js                 # CLI entry point
+├── docs/                         # Documentation and Guides
+│   ├── README.md                 # Package overview
+│   ├── QUICK_START.md            # Quick start guide
+│   ├── AIFLOW.md                 # Workflow (5 Gates) detail
+│   ├── CHANGELOG.md              # Version history
+│   ├── IMPLEMENTATION_SUMMARY.md # Technical implementation details
+│   ├── getting-started.md
+│   ├── architecture.md
+│   ├── configuration.md
+│   ├── cli-reference.md
+│   ├── troubleshooting.md
+│   └── workflows/
+│       ├── bug-fix.md
+│       ├── feature.md
+│       ├── investigation.md
+│       ├── refactor.md
+│       └── impact-analysis.md
 ├── scripts/
 │   ├── init.js                   # Project initialization
 │   ├── update.js                 # Version management
@@ -196,50 +212,16 @@ ai-flow-kit/
 │   └── memory.js                 # Knowledge management
 ├── custom/
 │   ├── skills/                   # Team-specific skills
-│   │   ├── investigate-bug/
-│   │   ├── impact-analysis/
-│   │   ├── generate-spec/
-│   │   └── report-customer/
 │   ├── rules/                    # Team standards
-│   │   ├── code-style.md
-│   │   ├── naming.md
-│   │   └── review-checklist.md
-│   ├── templates/                # Framework rules
-│   │   ├── laravel.md
-│   │   ├── nextjs.md
-│   │   └── vue-nuxt.md
+│   ├── templates/                # Tool templates
 │   ├── prompts/                  # Task templates
-│   │   ├── bug-fix.md
-│   │   ├── feature.md
-│   │   └── investigation.md
 │   └── mcp-presets/              # MCP adapters
-│       ├── jira.json
-│       ├── backlog.json
-│       ├── google-sheets.json
-│       └── README.md
 ├── upstream/                     # Original obra/superpowers
-│   ├── skills/
-│   ├── agents/
-│   └── commands/
-├── docs/
-│   ├── getting-started.md
-│   ├── architecture.md
-│   ├── configuration.md
-│   ├── cli-reference.md
-│   ├── troubleshooting.md
-│   └── workflows/
-│       ├── bug-fix.md
-│       ├── feature.md
-│       ├── investigation.md
-│       ├── refactor.md
-│       └── impact-analysis.md
 ├── package.json                  # Updated with metadata
 ├── .gitignore                    # Updated
 ├── .aiflowrc.json.example        # Configuration template
-├── README.md                     # Complete documentation
-├── QUICK_START.md                # Quick getting started
-├── CONTRIBUTING.md               # Contribution guide
-└── index.js                      # Main entry point
+├── index.js                      # Main entry point
+└── plan.md                       # TechLead planning (root)
 ```
 
 ## 🎯 Key Features Summary

package/{QUICK_START.md → docs/QUICK_START.md}

@@ -1,6 +1,6 @@
 # Quick Start — AI Flow Kit
 
-> Full workflow: [AIFLOW.md](./AIFLOW.md) | Contributing: [CONTRIBUTING.md](./CONTRIBUTING.md)
+> Full workflow: [AIFLOW.md](./AIFLOW.md)
 
 ---
 
@@ -103,7 +103,7 @@ claude                        # AI auto-starts Gate 1 immediately
 > **Multi-Tool Support:**
 > - If using **Cursor**: Gate Workflow is enforced via `.cursorrules`.
 > - If using **Gemini CLI**: Rules are loaded from `GEMINI.md`.
-> - The AI will automatically detect if you are mid-task by reading `.claude/context/current.json`.
+> - The AI will automatically detect if you are mid-task by reading `.aiflow/context/current.json`.
 
 ### Step 3: GATE 1 — AI Analyzes Requirement
 
@@ -111,7 +111,7 @@ claude                        # AI auto-starts Gate 1 immediately
 
 When you open Claude, AI will **automatically** start analyzing:
 
-1. **Read ticket** from `.claude/context/current.json`
+1. **Read ticket** from `.aiflow/context/current.json`
 2. **Read source code** — understand architecture, related files, data flow
 3. **Ask clarifying questions** (one at a time) if anything is unclear
 4. **Output** `plan/PROJ-33/requirement.md` containing:
@@ -348,14 +348,14 @@ After installing `ai-flow-kit`, these docs are available:
 | [QUICK_START.md](./QUICK_START.md) | This file — step-by-step guide for developers |
 | [AIFLOW.md](./AIFLOW.md) | Complete 5-Gate workflow: who does what, outputs, templates |
 | [README.md](./README.md) | Package overview, architecture, all features |
-| [CONTRIBUTING.md](./CONTRIBUTING.md) | How to add skills, templates, adapters, rules |
+| [CHANGELOG.md](./CHANGELOG.md) | Version history |
 | [IMPLEMENTATION_SUMMARY.md](./IMPLEMENTATION_SUMMARY.md) | Technical implementation details |
-| [docs/workflows/](./docs/workflows/) | Per-task-type workflow guides |
-| [docs/architecture.md](./docs/architecture.md) | System architecture |
-| [docs/cli-reference.md](./docs/cli-reference.md) | CLI command reference |
-| [docs/configuration.md](./docs/configuration.md) | Configuration guide |
-| [docs/troubleshooting.md](./docs/troubleshooting.md) | Common issues & fixes |
-| [docs/getting-started.md](./docs/getting-started.md) | Getting started guide |
+| [workflows/](./workflows/) | Per-task-type workflow guides |
+| [architecture.md](./architecture.md) | System architecture |
+| [cli-reference.md](./cli-reference.md) | CLI command reference |
+| [configuration.md](./configuration.md) | Configuration guide |
+| [troubleshooting.md](./troubleshooting.md) | Common issues & fixes |
+| [getting-started.md](./getting-started.md) | Getting started guide |
 
 Access docs after install:
 ```bash

package/{README.md → docs/README.md}

@@ -25,10 +25,9 @@ Developers only need a single command to load ticket context → AI automaticall
 
 - **[Quick Start Guide](./QUICK_START.md)** — Step-by-step instructions for developers.
 - **[Full Workflow (5 Gates)](./AIFLOW.md)** — In-depth look at the Gate process.
-- **[Developer Onboarding](./docs/developer-overview.md)** — Presentation-ready guide for new team members.
-- **[Contributing Guide](./CONTRIBUTING.md)** — How to extend with new skills/templates.
-- **[Troubleshooting](./docs/troubleshooting.md)** — Common issues and fixes.
-- **[Integration Guide](./docs/ai-integration.md)** — Advanced tool setup (Claude, Cursor, Gemini).
+- **[Developer Onboarding](./developer-overview.md)** — Presentation-ready guide for new team members.
+- **[Troubleshooting](./troubleshooting.md)** — Common issues and fixes.
+- **[Integration Guide](./ai-integration.md)** — Advanced tool setup (Claude, Cursor, Gemini).
 
 ---
 
@@ -154,7 +153,7 @@ aiflow init --framework spring-boot,reactjs --adapter backlog,jira
 
 ### `aiflow use <ticket>`
 
-Load ticket context into `.claude/context/current.json`.
+Load ticket context into `.aiflow/context/current.json`.
 
 ```bash
 # Backlog
@@ -282,6 +281,12 @@ aiflow memory --list
 ```
 ai-flow-kit/
 ├── bin/aiflow.js                    # CLI entry
+├── docs/                            # Documentation and Guides
+│   ├── README.md                    # Main documentation
+│   ├── QUICK_START.md               # Quick start guide
+│   ├── AIFLOW.md                    # Workflow (5 Gates) detail
+│   ├── CHANGELOG.md                 # Version history
+│   └── ...                          # Other guides
 ├── scripts/
 │   ├── init.js                      # Project initialization
 │   ├── update.js                    # Version management
@@ -297,7 +302,7 @@ ai-flow-kit/
 │   ├── rules/java/                  # Java/Spring Boot rules
 │   ├── rules/php/                   # PHP/Laravel rules
 │   ├── rules/javascript/            # JS/TS rules
-│   ├── templates/                   # Framework CLAUDE.md templates
+│   ├── templates/                   # Framework tool templates
 │   ├── prompts/                     # Task prompt templates
 │   └── mcp-presets/                 # Backlog/Jira/Sheets config
 └── upstream/                        # obra/superpowers (inherited)
@@ -347,4 +352,4 @@ aiflow init --adapter backlog
 aiflow doctor
 ```
 
-See more: [docs/troubleshooting.md](./docs/troubleshooting.md)
+See more: [docs/troubleshooting.md](./troubleshooting.md)

package/docs/ai-integration.md

@@ -1,53 +1,53 @@
-# Multi-AI Environment Integration
-
-`ai-flow-kit` is designed to be tool-agnostic. While it works best with Claude Code CLI due to deep MCP integration, you can use it with any AI tool.
-
-## Supported Environments
-
-| Tool | Instruction File | Support Level | Key Features |
-|------|------------------|---------------|--------------|
-| **Claude Code** | `CLAUDE.md` | Native (Best) | Auto-triggers, full MCP access, session hooks. |
-| **Cursor** | `.cursorrules` | High | Project-wide rules, `@Codebase` context. |
-| **Gemini CLI** | `GEMINI.md` | Medium | System instructions support. |
-| **GitHub Copilot** | `.github/copilot-instructions.md` | Medium | Inline suggestions, custom instructions. |
-| **OpenCode / Generic** | `AI_INSTRUCTIONS.md` | General | Manual context loading. |
-
----
-
-## Tool-Specific Setup
-
-### 1. Cursor AI
-When you run `aiflow init`, it generates a `.cursorrules` file. 
-- Cursor will automatically read this file to understand the **Gate Workflow**.
-- Use `@Codebase` when you need the AI to search across your whole project.
-- **Resumption**: If you start a task in Claude Code and switch to Cursor, Cursor will see the generated `plan/` files and resume from where you left off.
-
-### 2. Gemini CLI
-Pass `GEMINI.md` as system instructions to your Gemini session.
-- **Tip**: Always ensure the AI reads `.claude/context/current.json` first to load the ticket context.
-- Gemini is excellent for large context analysis during Gate 1.
-
-### 3. GitHub Copilot / Codex
-Copilot uses `.github/copilot-instructions.md` to guide its suggestions.
-- This ensures that Copilot's inline completions follow your project's architecture and team rules.
-
----
-
-## Cross-Tool State Resumption
-The "Secret Sauce" of `ai-flow-kit` is its file-based state management:
-
-1. **Context**: Saved in `.claude/context/current.json`.
-2. **Progress**: Saved as Markdown docs in `plan/[ticket-id]/`.
-3. **Rules**: Saved in `.rules/`.
-
-Because these are standard files, any AI tool can read them. You can:
-1. Start **Gate 1** (Analysis) in Claude Code.
-2. Review and **Approve** the requirement doc.
-3. Switch to **Cursor** for **Gate 3** (Coding) because you prefer the IDE integrations.
-4. Switch back to **Claude Code** for **Gate 4** (Self-Review) to use its automated testing power.
-
----
-
-## Best Practices
-- **Always Approve Docs**: Ensure `requirement.md` and `plan.md` are approved (you can just type "APPROVED" in the chat or edit the file to say so).
-- **Update Status**: If you make progress in a tool that doesn't have hooks, manually update the `summary.md` or the ticket status.
+# Multi-AI Environment Integration
+
+`ai-flow-kit` is designed to be tool-agnostic. While it works best with Claude Code CLI due to deep MCP integration, you can use it with any AI tool.
+
+## Supported Environments
+
+| Tool | Instruction File | Support Level | Key Features |
+|------|------------------|---------------|--------------|
+| **Claude Code** | `CLAUDE.md` | Native (Best) | Auto-triggers, full MCP access, session hooks. |
+| **Cursor** | `.cursorrules` | High | Project-wide rules, `@Codebase` context. |
+| **Gemini CLI** | `GEMINI.md` | Medium | System instructions support. |
+| **GitHub Copilot** | `.github/copilot-instructions.md` | Medium | Inline suggestions, custom instructions. |
+| **OpenCode / Generic** | `AI_INSTRUCTIONS.md` | General | Manual context loading. |
+
+---
+
+## Tool-Specific Setup
+
+### 1. Cursor AI
+When you run `aiflow init`, it generates a `.cursorrules` file. 
+- Cursor will automatically read this file to understand the **Gate Workflow**.
+- Use `@Codebase` when you need the AI to search across your whole project.
+- **Resumption**: If you start a task in Claude Code and switch to Cursor, Cursor will see the generated `plan/` files and resume from where you left off.
+
+### 2. Gemini CLI
+Pass `GEMINI.md` as system instructions to your Gemini session.
+- **Tip**: Always ensure the AI reads `.aiflow/context/current.json` first to load the ticket context.
+- Gemini is excellent for large context analysis during Gate 1.
+
+### 3. GitHub Copilot / Codex
+Copilot uses `.github/copilot-instructions.md` to guide its suggestions.
+- This ensures that Copilot's inline completions follow your project's architecture and team rules.
+
+---
+
+## Cross-Tool State Resumption
+The "Secret Sauce" of `ai-flow-kit` is its file-based state management:
+
+1. **Context**: Saved in `.aiflow/context/current.json`.
+2. **Progress**: Saved as Markdown docs in `plan/[ticket-id]/`.
+3. **Rules**: Saved in `.rules/`.
+
+Because these are standard files, any AI tool can read them. You can:
+1. Start **Gate 1** (Analysis) in Claude Code.
+2. Review and **Approve** the requirement doc.
+3. Switch to **Cursor** for **Gate 3** (Coding) because you prefer the IDE integrations.
+4. Switch back to **Claude Code** for **Gate 4** (Self-Review) to use its automated testing power.
+
+---
+
+## Best Practices
+- **Always Approve Docs**: Ensure `requirement.md` and `plan.md` are approved (you can just type "APPROVED" in the chat or edit the file to say so).
+- **Update Status**: If you make progress in a tool that doesn't have hooks, manually update the `summary.md` or the ticket status.

package/docs/architecture.md

@@ -233,7 +233,7 @@ aiflow use JIRA-123
 [Load from MCP Adapter]
   - Fetch issue from Jira
   - Parse description, criteria
-  - Save to .claude/context/current.json
+  - Save to .aiflow/context/current.json
   ↓
 aiflow prompt bug-fix
   ↓
@@ -329,10 +329,9 @@ ai-flow-kit/
 │   │   └── refactor.md
 │   └── troubleshooting.md
 │
+├── docs/                         # Documentation
 ├── package.json
-├── README.md
-├── CONTRIBUTING.md
-└── .gitignore
+└── index.js
 ```
 
 ## Customization Points
@@ -340,7 +339,7 @@ ai-flow-kit/
 ### Add a Custom Skill
 
 1. Create `custom/skills/my-skill/SKILL.md`
-2. Follow [skill format](../CONTRIBUTING.md#1-add-a-custom-skill)
+2. Follow skill format (see technical documentation)
 3. Run `aiflow update` to activate
 4. Skill appears in `.claude/skills/`
 
@@ -374,7 +373,7 @@ The system is designed to extend:
 - **Validators:** Check output quality
 - **Plugins:** Custom commands and functionality
 
-See [Contributing Guide](../CONTRIBUTING.md) for details.
+See technical documentation for details.
 
 ## Best Practices
 

package/docs/cli-reference.md

@@ -80,7 +80,7 @@ aiflow use 1.0.0
 **What it does:**
 1. Fetches context from MCP adapter (if applicable)
 2. Parses and validates context
-3. Saves to `.claude/context/current.json`
+3. Saves to `.aiflow/context/current.json`
 4. Updates state tracking
 
 **Example:**
@@ -90,7 +90,7 @@ Fetching context from Jira...
 ✓ Title: Fix payment processing error
 ✓ Description: 2000+ words pulled
 ✓ Acceptance criteria: 3 items
-✓ Saved to .claude/context/current.json
+✓ Saved to .aiflow/context/current.json
 
 Ready to prompt! Run: aiflow prompt bug-fix
 ```