@codyswann/lisa 1.6.0 → 1.7.1

package/all/copy-overwrite/.claude/commands/project/bootstrap.md

@@ -7,38 +7,22 @@ Complete all of the following steps for $ARGUMENTS:
 
 ## Step 1: Setup
 
-Run `/project:setup $ARGUMENTS` directly (not via Task tool).
-- Creates project directory, brief.md, findings.md, git branch
-- Creates `.claude-active-project` marker file
-- Outputs the project name (e.g., `2026-01-26-my-feature`)
+Run `/project:setup $ARGUMENTS`
 
 Capture the project name from the output for use in subsequent steps.
 
-## Step 2: Create and Execute Tasks
+## Step 2: Research
 
-Create workflow tracking tasks with `metadata.project` set to the project name from Step 1:
+Run `/project:research @projects/<project-name>`
 
-```
-TaskCreate:
-  subject: "Research project requirements"
-  description: "Run /project:research projects/<project-name> to gather codebase and web research."
-  metadata: { project: "<project-name-from-step-1>" }
+## Step 3: Gap Detection
 
-TaskCreate:
-  subject: "Gap detection and execution"
-  description: "Read projects/<project-name>/research.md. Check '## Open Questions' section. If unresolved questions exist, STOP and report to human. If no gaps, immediately run /project:execute @projects/<project-name>"
-  metadata: { project: "<project-name-from-step-1>" }
-```
+Read @projects/<project-name>/research.md. 
 
-**Execute each task via a subagent** to preserve main context. Launch up to 6 in parallel where tasks don't have dependencies. Do not stop until both are completed.
+Check '## Open Questions' section. If unresolved questions exist, STOP and report to human. 
+
+If no gaps, immediately run `/project:execute @projects/<project-name>`
 
 ## Output to Human
 
 - If gaps exist: "⚠️ Bootstrap complete but needs human review - see Open Questions in research.md"
-- If no gaps: Execution will begin automatically
-
----
-
-## Next Step
-
-After completing this phase, tell the user: "To continue, run `/project:execute @projects/<project-name>`"

package/all/copy-overwrite/.claude/commands/project/debrief.md

@@ -40,10 +40,4 @@ TaskCreate:
 - Are simple "never do X" or "always do Y" statements
 - Cannot be scoped to a skill that's invoked on-demand
 
-If a learning only applies to certain types of work (e.g., "when writing GraphQL resolvers..."), it should be a **skill** instead, not a rule.
-
----
-
-## Next Step
-
-After completing this phase, tell the user: "To continue, run `/project:archive $ARGUMENTS`"
+If a learning only applies to certain types of work (e.g., "when writing GraphQL resolvers..."), it should be a **skill** instead, not a rule.

package/all/copy-overwrite/.claude/commands/project/document.md

@@ -0,0 +1,51 @@
+---
+description: Updates all documentation related to changes implemented in the project
+argument-hint: <project-directory>
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, Skill
+---
+
+The current branch is a feature branch with implementation of the project in $ARGUMENTS.
+
+Changes on this branch need corresponding documentation updates to keep README, API docs, changelogs, and JSDoc current.
+
+**IMPORTANT**: Perform each step and move to the next without stopping.
+
+## Setup
+
+Set active project marker: `echo "$ARGUMENTS" | sed 's|.*/||' > .claude-active-project`
+
+Extract `<project-name>` from the last segment of `$ARGUMENTS`.
+
+## Create and Execute Tasks
+
+Create workflow tracking tasks with `metadata.project` set to the project name:
+
+```
+TaskCreate:
+  subject: "Identify changed files and documentation targets"
+  description: "Use git to identify files changed on this branch (git diff main...HEAD --name-only). For each changed file, identify related documentation: README sections, API docs, inline JSDoc, CHANGELOG entries, architecture docs, configuration docs. Compile a mapping of: changed file → related documentation file(s). Save to $ARGUMENTS/doc-targets.json with structure: { \"file.ts\": [\"README.md#section\", \"docs/api.md\"], ... }"
+  metadata: { project: "<project-name>" }
+
+TaskCreate:
+  subject: "Update README and user-facing docs"
+  description: "For each documentation target in $ARGUMENTS/doc-targets.json that is a README section or user guide: Read the changed implementation file. Read the current documentation section. Update the documentation to accurately reflect the new/changed behavior, examples, or configuration. Preserve existing structure and tone."
+  metadata: { project: "<project-name>" }
+
+TaskCreate:
+  subject: "Update API and technical documentation"
+  description: "For each documentation target that is API docs, architecture docs, or technical guides: Read the changed implementation. Read the current documentation. Update to reflect new endpoints, parameters, type signatures, behavior changes, or architectural decisions. Ensure consistency with code comments."
+  metadata: { project: "<project-name>" }
+
+TaskCreate:
+  subject: "Update CHANGELOG"
+  description: "If CHANGELOG.md or CHANGELOG.{md,txt,rst} exists in project root: Add entry for all user-facing changes. Group by type (Added, Changed, Fixed, Deprecated). Reference relevant files or features. Follow existing CHANGELOG format and conventions."
+  metadata: { project: "<project-name>" }
+
+TaskCreate:
+  subject: "Verify JSDoc on changed files"
+  description: "Read $ARGUMENTS/doc-targets.json. For each changed file (key), verify its JSDoc preamble and function/export documentation are current: Run /jsdoc-best-practices skill. Check that file-level preambles explain the module's purpose and when to use it. Check that exported functions/types have 'why' documentation (not just 'what'). Update any stale or missing documentation."
+  metadata: { project: "<project-name>" }
+```
+
+**Execute each task via a subagent** to preserve main context. Launch up to 5 in parallel where tasks don't have dependencies. Do not stop until all are completed.
+

package/all/copy-overwrite/.claude/commands/project/execute.md

@@ -41,6 +41,11 @@ TaskCreate:
   description: "Run /project:review $ARGUMENTS to review code changes."
   metadata: { project: "<project-name>" }
 
+TaskCreate:
+  subject: "Documentation"
+  description: "Run /project:document $ARGUMENTS to update documentation related to changes."
+  metadata: { project: "<project-name>" }
+
 TaskCreate:
   subject: "Verification"
   description: "Run /project:verify $ARGUMENTS to verify all requirements are met."
@@ -60,9 +65,3 @@ TaskCreate:
 **Execute each task via a subagent** to preserve main context. Launch up to 6 in parallel where tasks don't have dependencies. Do not stop until all are completed.
 
 Report "Project complete and archived" when done.
-
----
-
-## Next Step
-
-The project workflow is now complete. The implementation is done, reviewed, verified, learnings captured, and the project is archived.

package/all/copy-overwrite/.claude/commands/project/plan.md

@@ -171,9 +171,3 @@ Use **TaskList** to show the created tasks.
 ---
 
 **IMPORTANT**: Each task description should contain all necessary information from `brief.md` and `research.md` to complete in isolation. Tasks should be independent and as small in scope as possible.
-
----
-
-## Next Step
-
-After completing this phase, tell the user: "To continue, run `/project:implement $ARGUMENTS`"

package/all/copy-overwrite/.claude/commands/project/research.md

@@ -163,9 +163,3 @@ Run `/git:commit`
 - Focus on finding concrete file paths and line numbers
 - Each sub-agent prompt should be specific and focused on read-only documentation
 - **REMEMBER**: Document what IS, not what SHOULD BE
-
----
-
-## Next Step
-
-After completing this phase, tell the user: "To continue, run `/project:plan $ARGUMENTS`"

package/all/copy-overwrite/.claude/commands/project/review.md

@@ -46,9 +46,3 @@ TaskCreate:
 ```
 
 **Execute each task via a subagent** to preserve main context. Launch up to 6 in parallel where tasks don't have dependencies. Do not stop until all are completed.
-
----
-
-## Next Step
-
-After completing this phase, tell the user: "To continue, run `/project:verify $ARGUMENTS`"

package/all/copy-overwrite/.claude/commands/project/verify.md

@@ -39,9 +39,3 @@ TaskCreate:
 ```
 
 **Execute each task via a subagent** to preserve main context. Launch up to 6 in parallel where tasks don't have dependencies. Do not stop until all are completed.
-
----
-
-## Next Step
-
-After completing this phase, tell the user: "To continue, run `/project:debrief $ARGUMENTS`"

package/package.json

@@ -80,7 +80,7 @@
     "@ast-grep/cli"
   ],
   "name": "@codyswann/lisa",
-  "version": "1.6.0",
+  "version": "1.7.1",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "bin": {