@codyswann/lisa 1.17.0 → 1.18.1

package/all/copy-overwrite/.claude/hooks/track-plan-sessions.sh

@@ -15,6 +15,10 @@
 # Marker files: $PLANS_DIR/.active-plan-<session-id> contain the absolute path to the
 # active plan file. Stale markers (>24h) are cleaned up on each invocation.
 #
+# Dedup: Session ID dedup is scoped to the ## Sessions section only, not the entire
+# file. This prevents false positives when session IDs appear elsewhere in plan content
+# (e.g., scratchpad directory paths like /private/tmp/claude-501/.../SESSION_ID/...).
+#
 # Debug logging: All key decisions are logged to $PLANS_DIR/.track-plan-debug.log for
 # diagnostics if session IDs land in the wrong plan file.
 #
@@ -123,9 +127,11 @@ if [[ ! -f "$PLAN_FILE" ]]; then
   exit 0
 fi
 
-# Check if session ID already exists in the file (dedup)
-if grep -qF "$SESSION_ID" "$PLAN_FILE" 2>/dev/null; then
-  log_debug "dedup: session ID already in $PLAN_FILE (resolved via $RESOLUTION_METHOD), skipping write"
+# Check if session ID already exists in the ## Sessions section (dedup)
+# Only search within the Sessions section to avoid false positives from session IDs
+# appearing in plan content (e.g., scratchpad paths contain session IDs)
+if sed -n '/^## Sessions$/,$p' "$PLAN_FILE" 2>/dev/null | grep -qF "$SESSION_ID"; then
+  log_debug "dedup: session ID already in $PLAN_FILE sessions section (resolved via $RESOLUTION_METHOD), skipping write"
   exit 0
 fi
 

package/all/copy-overwrite/.claude/rules/plan.md

@@ -10,7 +10,7 @@ When making a plan:
 - Always make sure you understand the correct versions of third party libraries
 - Always save the plan with a name befitting the actual plan contents
 - Always look for code that can be reused for implementation
-- The plan MUST including written instructions to create a task list using TaskCreate for each task. The list should contain items related to the plan and specify that subagents should handle as many in parallel as possible. The following should always be included in the task list
+- The plan MUST include written instructions to create a task list using TaskCreate for each task (following the Task Creation Specification below). The list should contain items related to the plan and specify that subagents should handle as many in parallel as possible. The following should always be included in the task list
   - update/add/remove tests, containing the tests that need to get updated, added or removed
   - update/add/remove documentation (jsdocs, markdown files, etc), containing the documentation that need to get updated, added or removed
   - archive the plan (to be completed after all other tasks have been completed). This task should explcitly say to:
@@ -27,3 +27,53 @@ When making a plan:
 - If referencing a ticket (jira, linear, etc), always add a comment to the ticket with the finalized plan
 - The `## Sessions` section in plan files is auto-maintained by the `track-plan-sessions.sh` hook — do not manually edit it
 
+## Task Creation Specification
+
+When plans include TaskCreate instructions, each task must use this format:
+
+### Parameters
+
+- **subject**: Imperative form (e.g., "Add logout button to header")
+- **activeForm**: Present continuous form (e.g., "Adding logout button to header")
+
+### Description Template
+
+Every task description must be a markdown document with these sections:
+
+**Type:** Bug | Task | Epic | Story
+
+**Description:** Clear description based on type (Bug: symptoms/root cause; Story: Gherkin Given/When/Then; Task: clear goal; Epic: goal with sub-tasks)
+
+**Acceptance Criteria:** Checkbox list of completion criteria
+
+**Relevant Research:** Code references, patterns, architecture constraints extracted from research
+
+**Skills to Invoke:** `/coding-philosophy` is always required, plus other applicable skills
+
+**Implementation Details:** Files to modify, functions to implement, edge cases
+
+**Testing Requirements:** Unit tests (with `describe/it` structure), Integration tests, E2E tests (or "N/A")
+
+**Verification:** Every task MUST have empirical verification (see `verfication.md` for types). Include: verification type, proof command, and expected output.
+
+**Learnings:** On task completion, use `TaskUpdate` to save discoveries: `metadata: { learnings: ["Learning 1", ...] }`
+
+### Metadata
+
+```json
+{
+  "plan": "<plan-name>",
+  "type": "bug|task|epic|story",
+  "skills": ["/coding-philosophy", ...],
+  "verification": {
+    "type": "test|ui-recording|test-coverage|api-test|manual-check|documentation",
+    "command": "the proof command",
+    "expected": "what success looks like"
+  }
+}
+```
+
+### Task Sizing
+
+Each task must be small enough to have a **single, specific verification**. Ask: "Can I prove this is done with ONE command?" Split tasks that require multiple verifications.
+

package/all/copy-overwrite/README.md

@@ -0,0 +1,68 @@
+# [Project Name]
+
+Developers write specs and answer questions. Agents implement, test, verify, question, and document.
+
+## About This Project
+
+> Ask Claude: "What is the purpose of this project and how does it work?"
+
+## Step 1: Install Claude Code
+
+```bash
+brew install claude-code
+# Or: npm install -g @anthropic-ai/claude-code
+```
+
+## Step 2: Set Up This Project
+
+> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
+
+## Step 3: Run the App Locally
+
+> Ask Claude: "How do I start the app locally? Walk me through the steps and verify it's running."
+
+## Step 4: Work on a Feature
+
+> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
+
+Or break it down:
+
+- `/project:setup` - Set up the project from a spec or ticket
+- `/project:research` - Research the codebase
+- `/project:plan` - Create an implementation plan
+- `/project:implement` - Execute the plan
+- `/project:review` - Review the changes
+
+## Common Tasks
+
+### Code Review
+
+> Ask Claude: "Review the changes on this branch and suggest improvements."
+
+### Submit a PR
+
+> Ask Claude: "Commit my changes and open a pull request."
+
+### Fix Lint Errors
+
+> Ask Claude: "Run the linter and fix all errors."
+
+### Add Test Coverage
+
+> Ask Claude: "Increase test coverage for the files I changed."
+
+### Deploy
+
+> Ask Claude: "Walk me through deploying this project."
+
+## Project Standards
+
+> Ask Claude: "What coding standards and conventions does this project follow?"
+
+## Architecture
+
+> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
+
+## Troubleshooting
+
+> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/cdk/copy-overwrite/README.md

@@ -0,0 +1,76 @@
+# [Project Name]
+
+Developers write specs and answer questions. Agents implement, test, verify, question, and document.
+
+## About This Project
+
+> Ask Claude: "What is the purpose of this project and how does it work?"
+
+## Step 1: Install Claude Code
+
+```bash
+brew install claude-code
+# Or: npm install -g @anthropic-ai/claude-code
+```
+
+## Step 2: Set Up This Project
+
+> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
+
+## Step 3: Verify the Infrastructure
+
+> Ask Claude: "How do I synthesize the CDK stacks and verify the templates are valid?"
+
+## Step 4: Work on a Feature
+
+> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
+
+Or break it down:
+
+- `/project:setup` - Set up the project from a spec or ticket
+- `/project:research` - Research the codebase
+- `/project:plan` - Create an implementation plan
+- `/project:implement` - Execute the plan
+- `/project:review` - Review the changes
+
+## Common Tasks
+
+### Code Review
+
+> Ask Claude: "Review the changes on this branch and suggest improvements."
+
+### Submit a PR
+
+> Ask Claude: "Commit my changes and open a pull request."
+
+### Fix Lint Errors
+
+> Ask Claude: "Run the linter and fix all errors."
+
+### Add Test Coverage
+
+> Ask Claude: "Increase test coverage for the files I changed."
+
+### Synthesize CloudFormation Templates
+
+> Ask Claude: "Run CDK synth and verify the CloudFormation templates are generated correctly."
+
+### Diff Against Deployed Stacks
+
+> Ask Claude: "Run CDK diff to show what changes would be deployed compared to the current stacks."
+
+### Deploy
+
+> Ask Claude: "Walk me through deploying this project."
+
+## Project Standards
+
+> Ask Claude: "What coding standards and conventions does this project follow?"
+
+## Architecture
+
+> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
+
+## Troubleshooting
+
+> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/expo/copy-overwrite/README.md

@@ -0,0 +1,84 @@
+# [Project Name]
+
+Developers write specs and answer questions. Agents implement, test, verify, question, and document.
+
+## About This Project
+
+> Ask Claude: "What is the purpose of this project and how does it work?"
+
+## Step 1: Install Claude Code
+
+```bash
+brew install claude-code
+# Or: npm install -g @anthropic-ai/claude-code
+```
+
+## Step 2: Set Up This Project
+
+> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
+
+## Step 3: Run the App Locally
+
+> Ask Claude: "How do I start the app locally? Walk me through the steps and verify it's running."
+
+## Step 4: Work on a Feature
+
+> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
+
+Or break it down:
+
+- `/project:setup` - Set up the project from a spec or ticket
+- `/project:research` - Research the codebase
+- `/project:plan` - Create an implementation plan
+- `/project:implement` - Execute the plan
+- `/project:review` - Review the changes
+
+## Common Tasks
+
+### Code Review
+
+> Ask Claude: "Review the changes on this branch and suggest improvements."
+
+### Submit a PR
+
+> Ask Claude: "Commit my changes and open a pull request."
+
+### Fix Lint Errors
+
+> Ask Claude: "Run the linter and fix all errors."
+
+### Add Test Coverage
+
+> Ask Claude: "Increase test coverage for the files I changed."
+
+### Run on iOS
+
+> Ask Claude: "Start the app on the iOS simulator and verify it launches correctly."
+
+### Run on Android
+
+> Ask Claude: "Start the app on the Android emulator and verify it launches correctly."
+
+### Run on Web
+
+> Ask Claude: "Start the app in a web browser and verify it loads correctly."
+
+### Generate Types After Schema Changes
+
+> Ask Claude: "The API schema has changed. Regenerate types and fix any resulting type errors."
+
+### Deploy
+
+> Ask Claude: "Walk me through deploying this project."
+
+## Project Standards
+
+> Ask Claude: "What coding standards and conventions does this project follow?"
+
+## Architecture
+
+> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
+
+## Troubleshooting
+
+> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/nestjs/copy-overwrite/README.md

@@ -0,0 +1,76 @@
+# [Project Name]
+
+Developers write specs and answer questions. Agents implement, test, verify, question, and document.
+
+## About This Project
+
+> Ask Claude: "What is the purpose of this project and how does it work?"
+
+## Step 1: Install Claude Code
+
+```bash
+brew install claude-code
+# Or: npm install -g @anthropic-ai/claude-code
+```
+
+## Step 2: Set Up This Project
+
+> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
+
+## Step 3: Run the App Locally
+
+> Ask Claude: "How do I start the app locally? Walk me through the steps and verify it's running."
+
+## Step 4: Work on a Feature
+
+> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
+
+Or break it down:
+
+- `/project:setup` - Set up the project from a spec or ticket
+- `/project:research` - Research the codebase
+- `/project:plan` - Create an implementation plan
+- `/project:implement` - Execute the plan
+- `/project:review` - Review the changes
+
+## Common Tasks
+
+### Code Review
+
+> Ask Claude: "Review the changes on this branch and suggest improvements."
+
+### Submit a PR
+
+> Ask Claude: "Commit my changes and open a pull request."
+
+### Fix Lint Errors
+
+> Ask Claude: "Run the linter and fix all errors."
+
+### Add Test Coverage
+
+> Ask Claude: "Increase test coverage for the files I changed."
+
+### Run Database Migrations
+
+> Ask Claude: "Run pending database migrations and verify the schema is up to date."
+
+### Test API Endpoints
+
+> Ask Claude: "How do I test the API endpoints locally?"
+
+### Deploy
+
+> Ask Claude: "Walk me through deploying this project."
+
+## Project Standards
+
+> Ask Claude: "What coding standards and conventions does this project follow?"
+
+## Architecture
+
+> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
+
+## Troubleshooting
+
+> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/package.json

@@ -85,7 +85,7 @@
   },
   "resolutions": {},
   "name": "@codyswann/lisa",
-  "version": "1.17.0",
+  "version": "1.18.1",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "bin": {