@kienha/anti-chaotic 1.0.5 → 1.0.7

package/.agent/workflows/brainstorm.md

@@ -0,0 +1,81 @@
+---
+description: Analyze ideas with the user and create preliminary high-level documents (Roadmap, PRD).
+---
+
+# Brainstorm Workflow
+
+> [!IMPORTANT]
+> **MANDATORY**: Read `.agent/rules/documents.md` before creating any document.
+
+---
+
+## MCP Usage Guidelines
+
+| MCP Tool                                     | When to Use                                            | Example                           |
+| :------------------------------------------- | :----------------------------------------------------- | :-------------------------------- |
+| `mcp_sequential-thinking_sequentialthinking` | Analyze requirements, feature dependencies, trade-offs | Break down ambiguous requests     |
+| `mcp_context7_resolve-library-id`            | Find library ID before querying                        | "mermaid js"                      |
+| `mcp_context7_query-docs`                    | Research tech stack options, diagram syntax            | "Mermaid sequence diagram syntax" |
+
+---
+
+## Document Priority Order
+
+```
+Priority 0: Roadmap       ← Project Planning & Timeline
+Priority 1: PRD           ← Strategic Overview
+```
+
+---
+
+## Step 0: Clarification & Understanding
+
+**Role: Product Manager**
+
+> [!NOTE]
+> This step is **MANDATORY**. Do NOT proceed without user confirmation.
+
+> 💡 **MCP**: Use `sequential-thinking` to analyze ambiguous or complex requests
+
+1. **Invoke `[product-manager]` skill** to:
+   - Summarize understanding
+   - Create clarification questions
+2. Create `clarification-questions.md` artifact
+3. **WAIT** for user to review and confirm
+
+---
+
+## Step 1: Create Roadmap
+
+// turbo
+
+> 💡 **MCP**: Use `sequential-thinking` for phased planning and risk assessment
+
+1. **Invoke `[product-manager]` skill** to draft:
+   - Project timeline and milestones
+   - Phase breakdown (MVP, v1.0, v2.0)
+   - Key deliverables per phase
+2. Create `draft-roadmap.md` artifact
+3. After approval → Save to `docs/010-Planning/Roadmap-{ProjectName}.md`
+4. **WAIT** for user response
+
+---
+
+## Step 2: Create PRD
+
+// turbo
+
+1. **Invoke `[product-manager]` skill** to draft:
+   - Business objectives and success metrics
+   - Target audience/user personas
+   - Feature prioritization (MoSCoW)
+2. Create `draft-prd.md` artifact
+3. After approval → Save to `docs/020-Requirements/PRD-{ProjectName}.md`
+4. **WAIT** for user response
+
+---
+
+## Step 3: Transition to Documentation
+
+1. Present summary of created artifacts (Roadmap, PRD).
+2. Suggest next step: Run `/documentation` to generate detailed specifications (SDD, Epics, Stories).

package/.agent/workflows/custom-behavior.md

@@ -0,0 +1,64 @@
+---
+description: Workflow for safely customizing Agent rules and workflows with impact analysis and user confirmation.
+---
+
+# Custom Behavior Workflow
+
+## Tool Usage Guidelines
+
+| Tool            | When to Use                                          | Example Query                                                   |
+| --------------- | ---------------------------------------------------- | --------------------------------------------------------------- |
+| `find_by_name`  | Step 1: To find if a rule/workflow already exists    | `Pattern="*security*", SearchDirectory=".agent/rules"`          |
+| `view_file`     | Step 2: To read the existing content for comparison  | `AbsolutePath="/.../.agent/rules/security.md"`                  |
+| `notify_user`   | Step 3: To present analysis and ask for confirmation | `Message="I found an existing rule. Do you want to overwrite?"` |
+| `write_to_file` | Step 4: To create or overwrite the file              | `Overwrite=true`                                                |
+
+## Step 1: Identification & Search
+
+// turbo
+
+> 💡 **Tip**: Don't assume the file doesn't exist. Always search first.
+
+1.  Analyze the user's request to identify the _intent_ (e.g., "Add stricter linting", "Skip tests in deployment").
+2.  Search for existing Rules or Workflows that might already cover this.
+    - Rules: search in `.agent/rules/`
+    - Workflows: search in `.agent/workflows/`
+
+## Step 2: Impact Analysis
+
+> 💡 **Tip**: If a file exists, you MUST read it and compare it with the request.
+
+**Condition A: Target does NOT exist:**
+
+1.  Verify if a template exists in `.agent/assets/` or `references/` that could be used as a base.
+2.  Draft the new content in your memory.
+
+**Condition B: Target ALREADY exists:**
+
+1.  **Read** the current content of the file.
+2.  **Compare** the User's request vs the Current Content.
+3.  **Identify Conflicts**:
+    - Will this break existing constraints?
+    - Is this a "Breaking Change" or just an "Enhancement"?
+4.  **Formulate Recommendation**:
+    - _Adapt_: "I recommend creating a new file `custom-X.md` to avoid breaking standard X."
+    - _Override_: "This helps matches your specific need, but removes the safety check Y."
+
+## Step 3: User Confirmation
+
+> 💡 **Tip**: You must be explicit about what will change.
+
+1.  **Notify User** with a summary of your analysis.
+    - If **New**: "I will create a new rule [filename] that [does X]."
+    - If **modifying**: "I will modify [filename]. \n**Current**: [Summary of old]\n**Proposed**: [Summary of new]\n**Impact**: [Warning about side effects]"
+2.  **WAIT** for user approval.
+
+## Step 4: Execution
+
+1.  Perform the file operation (`write_to_file` or `replace_file_content`).
+2.  **Validate**: Read the file back to ensure syntax is correct (Markdown/YAML frontmatter).
+3.  **Register**: If it's a rule, remind the user if they need to manually activate it (unless it's `always_on`).
+
+## Step 5: Verification
+
+1. Check if the customization works as expected (if possible, by running a dry-run or asking user to test).

package/.agent/workflows/documentation.md

@@ -0,0 +1,123 @@
+---
+description: Generate comprehensive documentation (Architecture, API, Specs) from either Codebase or Requirements.
+---
+
+# Documentation Workflow
+
+> [!IMPORTANT]
+> **MANDATORY**: Apply `.agent/rules/documents.md` for all document creation.
+
+---
+
+## MCP Usage Guidelines
+
+| MCP Tool                                     | When to Use                                    |
+| :------------------------------------------- | :--------------------------------------------- |
+| `mcp_sequential-thinking_sequentialthinking` | Analyze complex architecture, design decisions |
+| `mcp_context7_query-docs`                    | Research framework patterns, diagram syntax    |
+
+---
+
+## Step 0: Determine Mode
+
+**Determine the source of truth:**
+
+1. **From Codebase**: Reverse engineer docs from existing code.
+2. **From Requirements**: Forward engineer detailed specs (SDD, Stories) from PRD/Roadmap.
+
+---
+
+# MODE A: From Codebase
+
+## Step A1: Codebase Discovery
+
+// turbo
+
+> 💡 **MCP**: Use `sequential-thinking` to analyze unfamiliar project structures
+
+1. **Invoke `[lead-architect]` skill** to analyze codebase structure
+2. Identify: tech stack, entry points, API routes, DB schemas
+3. **WAIT** for user to confirm understanding
+
+---
+
+## Step A2: Legacy Docs Generation (Architecture, API, Schema)
+
+// turbo
+
+1. **Invoke `[lead-architect]` skill** to create:
+   - System Context (C4 Context Diagram)
+   - Component View (C4 Component Diagram)
+2. **Invoke `[backend-developer]` skill** to:
+   - Document API endpoints
+   - Generate Entity Relationship Diagram (ERD)
+3. Save to `docs/030-Specs/` and `docs/030-Specs/Architecture/`
+
+---
+
+# MODE B: From Requirements
+
+**Prerequisite**: Existing PRD (from `/brainstorm`).
+
+## Step B1: Create SDD (System Design Document)
+
+// turbo
+
+> 💡 **MCP**:
+>
+> - **MUST** use `sequential-thinking` for architectural decisions
+> - Use `context7` with `/vercel/next.js`, `/supabase/supabase` for tech stack research
+
+1. **Invoke `[lead-architect]` skill** to draft:
+   - High-level system architecture
+   - Technology stack decisions
+   - Component diagram
+   - Data flow overview
+2. Create `draft-sdd.md` artifact
+3. After approval → Save to `docs/030-Specs/Architecture/SDD-{ProjectName}.md`
+
+---
+
+## Step B2: Create Epics & Use Cases
+
+// turbo
+
+1. **Invoke `[business-analysis]` skill** to:
+   - Break PRD features into Epics (`docs/022-User-Stories/Epics/`)
+   - Define Use Cases with Mermaid diagrams (`docs/020-Requirements/Use-Cases/`)
+2. Create artifacts for review before saving
+
+---
+
+## Step B3: Create User Stories
+
+// turbo
+
+1. **Invoke `[business-analysis]` skill** to create:
+   - User Stories with Acceptance Criteria (`docs/022-User-Stories/Backlog/`)
+   - Complexity estimates
+2. Create `draft-user-stories.md` artifact
+3. After approval → Save
+
+---
+
+## Step B4: Create ADRs (Optional)
+
+// turbo
+
+**Skip if**: User did not request ADRs.
+
+1. **Invoke `[lead-architect]` skill** to document technical decisions.
+2. Save to `docs/030-Specs/Architecture/ADR-{NNN}-{Decision}.md`
+
+---
+
+# Finalize
+
+## Step X: Finalize
+
+// turbo
+
+1. Create/update MOC files
+2. Validate wiki-links and frontmatter
+3. Present summary and suggest next steps (`/ui-ux-design` or `/implement-feature`)

package/.agent/workflows/implement-feature.md

@@ -1,13 +1,11 @@
 ---
-description: End-to-end feature implementation workflow (Spec → Design → Code → Test → Deploy)
+description: Orchestrates feature implementation from specification to deployment.
 ---
 
 # Feature Implementation Workflow
 
-Orchestrates feature implementation from specification to deployment.
-
 > [!IMPORTANT]
-> **MANDATORY**: Read `.agent/rules/documentation.md` before creating any document.
+> **MANDATORY**: Read `.agent/rules/documents.md` before creating any document.
 
 ---
 

package/.agent/workflows/ui-ux-design.md

@@ -1,13 +1,11 @@
 ---
-description: Transform requirement into UI/UX design (System → Components → Prototypes)
+description: Transform requirements into comprehensive UI/UX design deliverables.
 ---
 
 # UI/UX Design Workflow
 
-Transform requirements into comprehensive UI/UX design deliverables.
-
 > [!IMPORTANT]
-> **MANDATORY**: Apply `.agent/rules/documentation.md` for all documentation structure.
+> **MANDATORY**: Apply `.agent/rules/documents.md` for all documentation structure.
 
 ---
 

package/README.md

@@ -9,12 +9,25 @@
 
 ## 🎯 Introduction
 
-**Anti-Chaotic** is a comprehensive **Agent Kit** for Antigravity, designed to standardize and optimize your software development workflow. It serves as a versatile toolkit rather than a rigid framework:
+**Anti-Chaotic** is a comprehensive **Agent Kit** for Antigravity, designed to standardize and optimize your software development workflow.
 
-- 🧠 **12+ Multi-domain AI Skills** - From Product Manager, Business Analyst to Lead Architect, DevOps Engineer
-- 🔄 **5 Automated Workflows** - Pre-defined, reusable work processes
-- 📜 **Rules Engine** - A rule system that ensures AI Agents follow project standards
-- 📚 **References Library** - Documentation references for various technologies and frameworks
+### 🎯 Core Philosophy
+
+> **Process over Speed**: This kit is designed for **development teams** and **collaborative environments**. It prioritizes robust processes, structure, and long-term maintainability over "fast shipping" or quick hacks. It aims to bring standard engineering practices to AI-assisted coding.
+
+### 🧩 Concepts
+
+- **Skills = Knowledge**: What the agent knows (Best practices, languages, patterns).
+- **Rules & Workflows = Process**: How the agent executes (Steps, restrictions, output formats).
+
+_We encourage teams to customize these skills and define their own rules & workflows to align with their specific enterprise standards._
+
+### 📦 Components
+
+- 🧠 **12+ Multi-domain AI Skills** - From Product Manager, Business Analyst to Lead Architect.
+- 🔄 **6 Automated Workflows** - Pre-defined, reusable work processes.
+- 📜 **Rules Engine** - A rule system that ensures AI Agents follow project standards.
+- 📚 **References Library** - Documentation references for various technologies.
 
 ---
 
@@ -43,11 +56,20 @@
 - **Clean Code Rules**: Coding standards and best practices
 - **Project Rules**: Project-specific conventions
 
+> **ℹ️ Documentation & Tools**: The default generated documentation is optimized for **Obsidian**. If your team uses **Jira**, **GitHub**, or other tools, simply connect the relevant **MCP Server** and customize the `documents.md` rule to align the output format.
+
 ---
 
 ## 🚀 Quick Start
 
-### 1. Initialize in your project
+### 1. Recommended Setup (MCP Servers)
+
+To achieve the best results, we highly recommend installing the following MCP (Model Context Protocol) servers:
+
+- **[sequence-thinking](https://github.com/axiom-team/mcp-server-sequence-thinking)**: AI model for advanced problem breakdown and step-by-step reasoning.
+- **[context7](https://github.com/axiom-team/mcp-server-context7)**: For managing and retrieving broad project context.
+
+### 2. Initialize in your project
 
 Run the following command in your project root to install the Agent Kit:
 
@@ -57,29 +79,29 @@ npx @kienha/anti-chaotic init
 
 This will download the `.agent` folder containing all skills, rules, and workflows into your project.
 
-### 2. Using the Agent Kit
+### 3. Using the Agent Kit
 
 Once initialized, start a new chat with your AI IDE (Cursor, Windsurf, etc.) and reference the installed rules/workflows.
 
 #### Start a new project with AI:
 
 ```
-/requirement-analysis Create a sales management application for a fashion store
+/brainstorm Create a sales management application for a fashion store
 ```
 
 #### Generate docs for an existing project:
 
 ```
-/generate-docs-from-codebase
+/documentation
 ```
 
 #### Design UI from requirements:
 
 ```
-/ui-ux-design-from-doc docs/020-Requirements/PRD-YourProject.md
+/ui-ux-design docs/020-Requirements/PRD-YourProject.md
 ```
 
-### 3. Updating the Kit
+### 4. Updating the Kit
 
 To update your Agent Kit to the latest version:
 
@@ -96,19 +118,19 @@ npx @kienha/anti-chaotic update
 **Method 1: Slash Command**
 
 ```
-/requirement-analysis [Your project description]
+/brainstorm [Your project description]
 ```
 
 **Method 2: Direct Request**
 
 ```
-Please run the requirement-analysis workflow to analyze requirements for an e-commerce project
+Please run the brainstorm workflow to analyze requirements for an e-commerce project
 ```
 
 **Method 3: File Reference**
 
 ```
-Read and execute the workflow at .agent/workflows/requirement-analysis.md
+Read and execute the workflow at .agent/workflows/brainstorm.md
 ```
 
 ---
@@ -117,13 +139,14 @@ Read and execute the workflow at .agent/workflows/requirement-analysis.md
 
 ## 🔄 Automated Workflows
 
-| Workflow                           | Description                                                                                                   | Use Case                                                                        |
-| :--------------------------------- | :------------------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------ |
-| **`/requirement-analysis`**        | Analyzes raw requirements and generates detailed documentation (Roadmap, PRD, SDD, Epics, User Stories).      | Start of a new project or feature when you only have a rough idea.              |
-| **`/generate-docs-from-codebase`** | Scans the current codebase and generates comprehensive documentation (Architecture, API, Schema).             | Onboarding to a legacy project or updating docs after development.              |
-| **`/ui-ux-design-from-doc`**       | Transforms PRD/requirements documents into UI/UX design specifications, design systems, and visual artifacts. | After requirements are finalized, before coding.                                |
-| **`/workflow-rule-from-codebase`** | Analyzes the codebase to identify patterns and conventions, creating a project-specific rules file.           | Establishing coding standards for a new or existing team.                       |
-| **`/workflow-rule-from-feedback`** | Updates or creates rules based on user feedback to prevent recurring AI errors.                               | When the Agent makes repeated mistakes or you want to enforce a new preference. |
+| Workflow                 | Description                                                                                                | Use Case                                                            |
+| :----------------------- | :--------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------ |
+| **`/bootstrap`**         | Sets up project structure, installs dependencies, and configures environment based on architectural specs. | Start of Implementation Phase.                                      |
+| **`/brainstorm`**        | Analyze ideas with the user and create preliminary high-level documents (Roadmap, PRD).                    | Start of a new project or feature when you only have a rough idea.  |
+| **`/custom-behavior`**   | Safely customize Agent rules and workflows with impact analysis and user confirmation.                     | As needed to adjust Agent behavior or fix recurring mistakes.       |
+| **`/documentation`**     | Generate comprehensive documentation (Architecture, API, Specs) from either Codebase or Requirements.      | Onboarding to a legacy project OR creating detailed specs from PRD. |
+| **`/implement-feature`** | Orchestrates feature implementation from specification to deployment.                                      | After design and specs are ready, for actual coding and deployment. |
+| **`/ui-ux-design`**      | Transform requirements into comprehensive UI/UX design deliverables.                                       | After requirements are finalized, before coding.                    |
 
 ---
 
@@ -150,5 +173,3 @@ This project is released under the [MIT License](LICENSE).
 <p align="center">
   <b>Made with ❤️ for the AI-Driven Development Community</b>
 </p>
-
-> 💡 **Tip**: You can create new workflows by adding `.md` files in the `.agent/workflows/` directory following the same structure as existing workflows.

package/bin/anti-chaotic.js

@@ -26,6 +26,22 @@ program
         force: true,
       });
 
+      // Cleanup deprecated files
+      const deprecatedFiles = [
+        "rules/documentation.md",
+        "workflows/docs-from-codebase.md",
+        "workflows/requirement-analysis.md",
+        "workflows/setup-codebase.md",
+      ];
+
+      for (const file of deprecatedFiles) {
+        const filePath = path.join(targetAgentDir, file);
+        if (await fs.pathExists(filePath)) {
+          await fs.remove(filePath);
+          console.log(chalk.dim(`  Removed legacy file: ${file}`));
+        }
+      }
+
       console.log(
         chalk.green("✔ Successfully installed Anti-Chaotic Agent Kit."),
       );
@@ -70,6 +86,22 @@ program
         force: true,
       });
 
+      // Cleanup deprecated files
+      const deprecatedFiles = [
+        "rules/documentation.md",
+        "workflows/docs-from-codebase.md",
+        "workflows/requirement-analysis.md",
+        "workflows/setup-codebase.md",
+      ];
+
+      for (const file of deprecatedFiles) {
+        const filePath = path.join(targetAgentDir, file);
+        if (await fs.pathExists(filePath)) {
+          await fs.remove(filePath);
+          console.log(chalk.dim(`  Removed legacy file: ${file}`));
+        }
+      }
+
       console.log(chalk.green("✔ Successfully updated .agent from GitHub."));
       console.log(chalk.dim(`  Location: ${targetAgentDir}`));
     } catch (err) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kienha/anti-chaotic",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "Anti-Chaotic - An agent kit for Antigravity to standardize the software development process",
   "main": "index.js",
   "publishConfig": {

package/.agent/workflows/docs-from-codebase.md

@@ -1,104 +0,0 @@
----
-description: Generate comprehensive documentation from existing codebase (Architecture, API, Specs).
----
-
-# Generate Documentation from Codebase
-
-Automatically generates structured documentation from an existing codebase.
-
-> [!IMPORTANT]
-> **MANDATORY**: Apply `.agent/rules/documentation.md` for all document creation.
-
----
-
-## MCP Usage Guidelines
-
-| MCP Tool                                     | When to Use                                    |
-| -------------------------------------------- | ---------------------------------------------- |
-| `mcp_sequential-thinking_sequentialthinking` | Analyze complex architecture, design decisions |
-| `mcp_context7_query-docs`                    | Research framework patterns, diagram syntax    |
-
----
-
-## Step 1: Codebase Discovery
-
-// turbo
-
-> 💡 **MCP**: Use `sequential-thinking` to analyze unfamiliar project structures
-
-1. **Invoke `[lead-architect]` skill** to analyze codebase structure
-2. Identify: tech stack, entry points, API routes, DB schemas
-3. **WAIT** for user to confirm understanding
-
----
-
-## Step 2: Determine Scope
-
-// turbo
-
-Ask user which documentation to generate:
-
-- System Architecture
-- API Documentation
-- Database Schema
-- Component Reference
-
-**Default**: Generate all if not specified.
-
----
-
-## Step 3: Generate Architecture Documentation
-
-// turbo
-
-> 💡 **MCP**: Use `sequential-thinking` + `context7` with `/mermaid-js/mermaid` for C4 diagrams
-
-1. **Invoke `[lead-architect]` skill** to create:
-   - System Context (C4 Context Diagram)
-   - Component View (C4 Component Diagram)
-   - Data Flow documentation
-
----
-
-## Step 4: Generate API Documentation
-
-// turbo
-
-> 💡 **MCP**: Use `context7` for framework-specific API patterns
-
-1. **Invoke `[backend-developer]` skill** to:
-   - Scan and document API routes
-   - Create endpoint specifications
-
----
-
-## Step 5: Generate Database Schema Documentation
-
-// turbo
-
-> 💡 **MCP**: Use `context7` with `/drizzle-team/*` or `/prisma/*` + `/mermaid-js/mermaid` for ERD
-
-1. **Invoke `[backend-developer]` skill** to:
-   - Document entities and relationships
-   - Generate ERD diagram
-
----
-
-## Step 6: Finalize
-
-// turbo
-
-1. Create/update MOC files
-2. Validate wiki-links and frontmatter
-3. Present summary and suggest next steps
-
----
-
-## Quick Reference
-
-| Step | Skill             | Output            |
-| ---- | ----------------- | ----------------- |
-| 1    | lead-architect    | Codebase analysis |
-| 3    | lead-architect    | Architecture docs |
-| 4    | backend-developer | API docs          |
-| 5    | backend-developer | Schema docs       |