agile-context-engineering 0.1.0

package/commands/ace-refine-story.md

@@ -0,0 +1,90 @@
+# /ace:refine-story - Refine a Story for Execution
+
+Prepare a story for execution by creating detailed implementation tasks.
+
+## Usage
+
+```
+/ace:refine-story <story-id>
+/ace:refine-story E1-F1-S1
+```
+
+### Arguments
+
+- `story-id` - The story identifier to refine
+
+## Behavior
+
+This command prepares a story for execution by:
+- Researching the codebase to understand implementation
+- Breaking the story into atomic, executable tasks
+- Creating a task checklist for the executor
+- Identifying potential blockers
+
+## Instructions for Claude
+
+<ace-refine-story>
+
+### Prerequisites
+
+1. Verify ACE is initialized
+2. Read the story file
+3. Understand acceptance criteria
+
+### Refinement Process
+
+1. **Codebase Research**
+   - Find relevant existing code
+   - Understand patterns in use
+   - Identify integration points
+
+2. **Task Breakdown**
+   - Create atomic tasks (30 min - 2 hours each)
+   - Tasks should be independently committable
+   - Each task has clear done criteria
+
+3. **For Each Task:**
+   - ID: T1, T2, T3...
+   - Description: What exactly to do
+   - Files: Which files to modify/create
+   - Done Criteria: How to verify completion
+
+4. **Update Story File**
+
+Add tasks section:
+
+```markdown
+## Tasks
+
+### T1: <Task Description>
+- **Files:** `path/to/file.ts`
+- **Done:** <verification criteria>
+- **Status:** Pending
+
+### T2: <Task Description>
+- **Files:** `path/to/file.ts`, `path/to/other.ts`
+- **Done:** <verification criteria>
+- **Status:** Pending
+```
+
+5. **Identify Blockers**
+   - Missing information
+   - External dependencies
+   - Questions for the user
+
+### Output
+
+```
+✓ Story E1-F1-S1 refined!
+
+Tasks:
+  T1: <Task Description>
+  T2: <Task Description>
+  T3: <Task Description>
+
+Blockers: [None | List of blockers]
+
+Ready for: /ace:execute-story E1-F1-S1
+```
+
+</ace-refine-story>

package/commands/ace-verify-story.md

@@ -0,0 +1,127 @@
+# /ace:verify-story - Verify a Completed Story
+
+Verify that a completed story meets all acceptance criteria.
+
+## Usage
+
+```
+/ace:verify-story <story-id>
+/ace:verify-story E1-F1-S1
+```
+
+### Arguments
+
+- `story-id` - The story identifier to verify
+
+## Behavior
+
+This command verifies a story by:
+- Checking all acceptance criteria are met
+- Running the full test suite
+- Reviewing code changes for quality
+- Confirming with the user
+
+## Instructions for Claude
+
+<ace-verify-story>
+
+### Prerequisites
+
+1. Verify ACE is initialized
+2. Verify story status is "Done" (executed)
+3. Read story acceptance criteria
+
+### Verification Process
+
+1. **Acceptance Criteria Check**
+
+   For each acceptance criterion:
+   - Verify it's implemented
+   - Test the behavior manually if possible
+   - Check for edge cases
+
+2. **Code Quality Review**
+
+   Review the commits:
+   ```bash
+   git log --oneline -10  # See recent commits
+   ```
+
+   Check for:
+   - Consistent code style
+   - Appropriate error handling
+   - No security vulnerabilities
+   - Tests included
+
+3. **Test Suite**
+
+   Run the full test suite:
+   ```bash
+   npm test  # or appropriate test command
+   ```
+
+4. **User Acceptance**
+
+   Present findings to user:
+   ```
+   Story: E1-F1-S1 - <Title>
+
+   Acceptance Criteria:
+   ✓ Given X, when Y, then Z
+   ✓ Given A, when B, then C
+   ? Edge case needs user verification
+
+   Code Changes:
+   - X files modified
+   - Y lines added
+   - Z tests added
+
+   Test Results: All passing
+
+   Ready for user acceptance testing?
+   ```
+
+5. **Mark as Verified**
+
+   If all criteria pass:
+   - Update story status to "Verified"
+   - Update STATE.md
+   - Update BACKLOG.md progress
+
+### Issue Handling
+
+If issues are found:
+
+1. **Minor Issues**
+   - Note them for user
+   - Offer to fix immediately
+
+2. **Major Issues**
+   - Document in story file
+   - Recommend re-execution
+   - Update story status to "Needs Work"
+
+### GitHub Integration (if enabled)
+
+- Close the story issue if verified
+- Add verification comment with summary
+
+### Output
+
+```
+✓ Story E1-F1-S1 verified!
+
+All acceptance criteria met:
+  ✓ Criterion 1
+  ✓ Criterion 2
+  ✓ Criterion 3
+
+Code Quality: Good
+Tests: 12 passing, 0 failing
+
+Story marked as Verified.
+
+Feature E1-F1 progress: 2/4 stories complete
+```
+
+</ace-verify-story>

package/package.json

@@ -0,0 +1,42 @@
+{
+  "name": "agile-context-engineering",
+  "version": "0.1.0",
+  "description": "ACE - Agile Context Engineering: A spec-driven development system for Claude Code, OpenCode, Gemini CLI, and Codex CLI with Agile workflows",
+  "main": "index.js",
+  "bin": {
+    "agile-context-engineering": "bin/install.js",
+    "ace": "bin/install.js"
+  },
+  "files": [
+    "bin",
+    "commands",
+    "agents",
+    "templates"
+  ],
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1"
+  },
+  "keywords": [
+    "claude-code",
+    "opencode",
+    "gemini-cli",
+    "codex-cli",
+    "openai",
+    "anthropic",
+    "google",
+    "agile",
+    "context-engineering",
+    "ai-coding",
+    "spec-driven",
+    "cli"
+  ],
+  "author": "",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/agile-context-engineering/ace"
+  },
+  "engines": {
+    "node": ">=16.7.0"
+  }
+}