@mindfoldhq/trellis 0.2.6 → 0.2.7

package/dist/templates/claude/agents/research.md

@@ -2,7 +2,7 @@
 name: research
 description: |
   Code and tech search expert. Pure research, no code modifications. Finds files, patterns, and tech solutions.
-tools: Read, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__get_code_context_exa, Skill
+tools: Read, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__get_code_context_exa, Skill, mcp__chrome-devtools__*
 model: opus
 ---
 # Research Agent

package/dist/templates/claude/commands/finish-work.md

@@ -37,7 +37,7 @@ pnpm test
 **Key Question**: 
 > "If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"
 
-If YES -> Update the relevant structure doc.
+If YES -> Update the relevant spec doc.
 
 ### 3. API Changes
 

package/dist/templates/claude/commands/onboard.md

@@ -316,7 +316,7 @@ I recommend reading through `.trellis/spec/` to familiarize yourself with the te
 If the developer wants help filling guidelines, create a feature to track this:
 
 ```bash
-./.trellis/scripts/task.sh create "Fill structure guidelines" --slug fill-structure-guidelines
+./.trellis/scripts/task.sh create "Fill spec guidelines" --slug fill-spec-guidelines
 ```
 
 Then systematically analyze the codebase and fill each guideline file:

package/dist/templates/claude/commands/parallel.md

@@ -77,9 +77,9 @@ Use when:
 Plan Agent will:
 1. Evaluate requirement validity (may reject if unclear/too large)
 2. Call research agent to analyze codebase
-3. Create and configure feature directory
+3. Create and configure task directory
 4. Write prd.md with acceptance criteria
-5. Output ready-to-use feature directory
+5. Output ready-to-use task directory
 
 After plan.sh completes, start the worktree agent:
 

package/dist/templates/cursor/commands/finish-work.md

@@ -26,7 +26,7 @@ pnpm test
 
 ### 2. Documentation Sync
 
-**Structure Docs**:
+**Spec Docs**:
 - [ ] Does `.trellis/spec/backend/` need updates?
   - New patterns, new modules, new conventions
 - [ ] Does `.trellis/spec/frontend/` need updates?
@@ -37,7 +37,7 @@ pnpm test
 **Key Question**: 
 > "If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"
 
-If YES -> Update the relevant structure doc.
+If YES -> Update the relevant spec doc.
 
 ### 3. API Changes
 
@@ -94,7 +94,7 @@ git diff --name-only
 
 | Oversight | Consequence | Check |
 |-----------|-------------|-------|
-| Structure docs not updated | Others don't know the change | Check .trellis/spec/ |
+| Spec docs not updated | Others don't know the change | Check .trellis/spec/ |
 | Migration not created | Schema out of sync | Check db/migrations/ |
 | Types not synced | Runtime errors | Check shared types |
 | Tests not updated | False confidence | Run full test suite |

package/dist/templates/cursor/commands/onboard.md

@@ -316,7 +316,7 @@ I recommend reading through `.trellis/spec/` to familiarize yourself with the te
 If the developer wants help filling guidelines, create a feature to track this:
 
 ```bash
-./.trellis/scripts/task.sh create "Fill structure guidelines" --slug fill-structure-guidelines
+./.trellis/scripts/task.sh create "Fill spec guidelines" --slug fill-spec-guidelines
 ```
 
 Then systematically analyze the codebase and fill each guideline file:

package/dist/templates/trellis/scripts/common/registry.sh

@@ -8,7 +8,7 @@
 #   registry_get_file        - Get registry file path
 #   registry_get_agent_by_id - Find agent by ID
 #   registry_get_agent_by_worktree - Find agent by worktree path
-#   registry_get_task_dir - Get feature dir for a worktree
+#   registry_get_task_dir - Get task dir for a worktree
 #   registry_remove_by_id    - Remove agent by ID
 #   registry_remove_by_worktree - Remove agent by worktree path
 #   registry_add_agent       - Add agent to registry
@@ -123,7 +123,7 @@ registry_search_agent() {
   return 1
 }
 
-# Get feature directory for a worktree
+# Get task directory for a worktree
 # Args: worktree_path, [repo_root]
 # Returns: task_dir value, or empty if not found
 registry_get_task_dir() {

package/dist/templates/trellis/scripts/multi-agent/create-pr.sh

@@ -43,7 +43,7 @@ while [[ $# -gt 0 ]]; do
       shift
       ;;
     -h|--help)
-      echo "Usage: $0 [feature-dir] [--dry-run]"
+      echo "Usage: $0 [task-dir] [--dry-run]"
       echo ""
       echo "Options:"
       echo "  --dry-run    Show what would be done without making changes"

package/dist/templates/trellis/scripts/task.sh

@@ -762,7 +762,7 @@ cmd_set_branch() {
   if [[ -z "$target_dir" ]] || [[ -z "$branch" ]]; then
     echo -e "${RED}Error: Missing arguments${NC}"
     echo "Usage: $0 set-branch <task-dir> <branch-name>"
-    echo "Example: $0 set-branch <dir> feature/my-task"
+    echo "Example: $0 set-branch <dir> task/my-task"
     exit 1
   fi
 
@@ -1048,7 +1048,7 @@ Examples:
   $0 create "Add login feature" --slug add-login
   $0 init-context .trellis/tasks/01-21-add-login backend
   $0 add-context <dir> implement .trellis/spec/backend/auth.md "Auth guidelines"
-  $0 set-branch <dir> feature/add-login
+  $0 set-branch <dir> task/add-login
   $0 start .trellis/tasks/01-21-add-login
   $0 create-pr                          # Uses current task
   $0 create-pr <dir> --dry-run          # Preview without changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindfoldhq/trellis",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "description": "AI capabilities grow like ivy — Trellis provides the structure to guide them along a disciplined path",
   "type": "module",
   "main": "./dist/index.js",