aidflow 1.0.1 → 1.1.0

package/README.md

@@ -18,7 +18,7 @@ Add to your Claude Code MCP configuration (`~/.claude/settings.json` or project
     "aidflow": {
       "command": "aidflow",
       "env": {
-        "DEVPILOT_ROOT": "/path/to/your/project"
+        "AIDFLOW_ROOT": "/path/to/your/project"
       }
     }
   }
@@ -34,14 +34,14 @@ Or run with npx (no install):
       "command": "npx",
       "args": ["-y", "aidflow"],
       "env": {
-        "DEVPILOT_ROOT": "/path/to/your/project"
+        "AIDFLOW_ROOT": "/path/to/your/project"
       }
     }
   }
 }
 ```
 
-> `DEVPILOT_ROOT` defaults to `process.cwd()` if not set.
+> `AIDFLOW_ROOT` defaults to `process.cwd()` if not set.
 
 ## What It Does
 
@@ -53,7 +53,7 @@ aidflow structures your Claude Code workflow into **sessions** - isolated units
 init -> /spec -> session create -> plan create -> work -> /review -> session complete -> /report
 ```
 
-1. **`init`** - Set up `.devpilot/` directory and configuration
+1. **`init`** - Set up `.aidflow/` directory and configuration
 2. **`/spec`** - Define project engineering foundations (SPEC.md)
 3. **`session create`** - Start a new work session
 4. **`plan create`** - Structured planning with multi-round requirements gathering
@@ -96,7 +96,7 @@ After `init`, your project gets:
 ```
 your-project/
   SPEC.md                    # Project engineering foundations (via /spec)
-  .devpilot/
+  .aidflow/
     config.yaml              # Configuration
     README.md                # Internal documentation
     sessions/                # Active sessions
@@ -119,22 +119,22 @@ your-project/
 
 ## Configuration
 
-`.devpilot/config.yaml`:
+`.aidflow/config.yaml`:
 
 ```yaml
 version: 1
 
 worktree:
   auto: false                # Auto-create worktree per session
-  path: ".devpilot/worktrees"
+  path: ".aidflow/worktrees"
   branch_prefix: ""          # e.g., "feature/", "fix/"
 
 session:
-  history_path: ".devpilot/history"
+  history_path: ".aidflow/history"
   date_format: "YYMMDD"     # or "YYYYMMDD"
 
 guides:
-  path: ".devpilot/guides"
+  path: ".aidflow/guides"
 ```
 
 ## Requirements

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aidflow",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "description": "Session-based development workflow MCP for Claude Code",
   "type": "module",
   "bin": {

package/templates/README.md

@@ -1,11 +1,11 @@
-# devpilot
+# aidflow
 
 Session-based development workflow manager for Claude Code.
 
 ## Directory Structure
 
 ```
-.devpilot/
+.aidflow/
   config.yaml     # Configuration
   sessions/       # Active sessions
     {name}/
@@ -28,17 +28,17 @@ Session-based development workflow manager for Claude Code.
 |-----|------|---------|-------------|
 | `version` | number | `1` | Config version |
 | `worktree.auto` | boolean | `false` | Auto-create worktree on session create |
-| `worktree.path` | string | `".devpilot/worktrees"` | Worktree storage path |
+| `worktree.path` | string | `".aidflow/worktrees"` | Worktree storage path |
 | `worktree.branch_prefix` | string | `""` | Branch name prefix (e.g., `"feature/"`, `"fix/"`) |
-| `session.history_path` | string | `".devpilot/history"` | Archive destination |
+| `session.history_path` | string | `".aidflow/history"` | Archive destination |
 | `session.date_format` | string | `"YYMMDD"` | Date format for archive names (`YYMMDD` or `YYYYMMDD`) |
-| `guides.path` | string | `".devpilot/guides"` | Guide documents path |
+| `guides.path` | string | `".aidflow/guides"` | Guide documents path |
 
 ---
 
 ## meta.json
 
-Session metadata. Automatically managed by devpilot.
+Session metadata. Automatically managed by aidflow.
 
 ```json
 {
@@ -47,7 +47,7 @@ Session metadata. Automatically managed by devpilot.
   "status": "active",
   "worktree": {
     "enabled": true,
-    "path": ".devpilot/worktrees/fix-auth-bug",
+    "path": ".aidflow/worktrees/fix-auth-bug",
     "branch": "fix-auth-bug"
   }
 }
@@ -113,7 +113,7 @@ Progress is tracked via checkboxes. `session status` reports completion rate.
 
 ## Guides
 
-Markdown files in `.devpilot/guides/`. Used for project-specific knowledge injection.
+Markdown files in `.aidflow/guides/`. Used for project-specific knowledge injection.
 
 - First line = title, second line = description
 - Use `guide list` to see available guides

package/templates/config.yaml

@@ -1,20 +1,20 @@
-# devpilot configuration
+# aidflow configuration
 version: 1
 
 worktree:
   # Auto-create worktree for every new session
   auto: false
   # Worktree storage path
-  path: ".devpilot/worktrees"
+  path: ".aidflow/worktrees"
   # Branch name prefix for worktrees (e.g., "feature/", "fix/", or empty)
   branch_prefix: ""
 
 session:
   # Archived session storage path
-  history_path: ".devpilot/history"
+  history_path: ".aidflow/history"
   # Date format for archive names (YYMMDD or YYYYMMDD)
   date_format: "YYMMDD"
 
 guides:
   # Guide documents path
-  path: ".devpilot/guides"
+  path: ".aidflow/guides"

package/templates/guides/getting-started.md

@@ -1,5 +1,5 @@
 # Getting Started
-Quick guide to using devpilot in this project.
+Quick guide to using aidflow in this project.
 
 ## Session Workflow
 
@@ -17,5 +17,5 @@ For isolated parallel work, create sessions with worktrees:
 
 ## Guides
 
-Add project-specific guides to `.devpilot/guides/` as markdown files.
+Add project-specific guides to `.aidflow/guides/` as markdown files.
 Use `guide list` to see available guides.

package/templates/skills/finish/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: finish
+description: Complete session - review, archive, report, and commit in one step.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash, WebSearch
+user-invokable: true
+---
+
+Complete the current session by running review, archive, report, and commit sequentially.
+Stop immediately at any step if a blocking issue is found.
+
+## Step 1: Review
+
+1. **Identify the active session**
+   - Use `session status` to find the current session and its changed files
+   - Read plan.md to understand what was intended
+
+2. **Code Review - Changed Files**
+   Read EVERY changed file and check:
+   - Does the implementation match plan.md requirements?
+   - Are there any incomplete TODOs or FIXMEs?
+   - Error handling: are edge cases covered?
+   - If SPEC.md exists, do changes follow its conventions?
+   - Are there any hardcoded values that should be configurable?
+   - Security: no exposed secrets, no injection vulnerabilities?
+
+3. **Consistency Check**
+   - Naming conventions consistent across new/modified code?
+   - Import patterns match existing codebase style?
+   - No duplicate logic that should be extracted?
+   - No dead code or unused imports left behind?
+
+4. **Test Coverage**
+   - Run existing tests: `npm test` (or project-specific command from SPEC.md)
+   - If tests fail, STOP here and report failures to the user
+
+5. **Plan Completion Audit**
+   - Check each Implementation Item and Acceptance Criteria in plan.md
+   - Ensure all `- [ ]` items are checked `- [x]` if completed
+   - Flag any genuinely unchecked items
+
+6. **Review Gate**
+   - If blocking issues found: present them with AskUserQuestion, offer "Fix now" / "Proceed anyway" / "Cancel"
+   - If "Fix now": fix issues, then restart from Step 1
+   - If "Cancel": stop entirely
+   - If no issues or "Proceed anyway": continue to Step 2
+
+## Step 2: Archive Session
+
+Run `session complete` to archive the session.
+- If it fails due to incomplete plan items, use `force: true`
+
+## Step 3: Generate Report
+
+1. Find the latest directory in `.aidflow/history/` (sorted by name, newest first)
+2. Read `meta.json` from that directory to get session metadata
+3. Read `plan.md` from that directory (if exists)
+4. Gather git commits for the session period:
+   - Use `created_at` and `completed_at` from meta.json as the time range
+   - Run: `git log --oneline --after="{created_at}" --before="{completed_at}"`
+5. Read the changed files listed in meta.json and briefly review each
+6. Write `report.md` in the history directory with this format:
+
+```markdown
+# {Session Name} - Report
+
+## Summary
+{1-2 line summary of what was accomplished}
+
+## Plan Completion
+{Plan items and their completion status, if plan existed}
+
+## Changed Files
+| File | Change Type | Description |
+|------|-------------|-------------|
+| path/to/file | modified/new/deleted | Brief description |
+
+## Key Decisions
+{Important technical decisions made during the work}
+
+## Issues & Observations
+{Any issues found, edge cases, or observations for future reference}
+
+## Duration
+- Started: {created_at}
+- Completed: {completed_at}
+- Commits: {number}
+```
+
+## Step 4: Git Commit
+
+1. Run `git status` and `git diff` to see all changes
+2. Stage relevant files (avoid .env, credentials, etc.)
+3. Draft a commit message following project conventions:
+   - Message in Korean
+   - NO Co-Authored-By or AI traces
+   - Format: short title + blank line + bullet point details (if needed)
+4. Present the commit message to the user with AskUserQuestion for approval
+5. Create the commit after approval
+
+## Step 5: SPEC.md Check
+
+Ask the user with AskUserQuestion:
+"This session introduced changes. Should SPEC.md be updated to reflect new patterns or conventions?"
+- If yes: run `/spec` to update
+- If no: done
+
+## Notes
+- Be thorough but practical in review - flag real issues, not style nitpicks
+- If the project has a linter/formatter, run it during review
+- Focus on correctness and completeness over perfection
+- Keep report descriptions concise but informative

package/templates/skills/report/SKILL.md

@@ -10,7 +10,7 @@ Generate a completion report for the most recently archived session.
 
 ## Steps
 
-1. Find the latest directory in `.devpilot/history/` (sorted by name, newest first)
+1. Find the latest directory in `.aidflow/history/` (sorted by name, newest first)
 2. Read `meta.json` from that directory to get session metadata
 3. Read `plan.md` from that directory (if exists)
 4. Gather git commits for the session period: