@mindfoldhq/trellis 0.1.9 → 0.2.1

package/dist/templates/claude/hooks/ralph-loop.py

@@ -14,7 +14,7 @@ Mechanism:
 
 State file: .trellis/.ralph-state.json
 - Tracks current iteration count per session
-- Resets when feature changes
+- Resets when task changes
 """
 
 import json
@@ -33,7 +33,7 @@ STATE_TIMEOUT_MINUTES = 30  # Reset state if older than this
 STATE_FILE = ".trellis/.ralph-state.json"
 WORKTREE_YAML = ".trellis/worktree.yaml"
 DIR_WORKFLOW = ".trellis"
-FILE_CURRENT_FEATURE = ".current-feature"
+FILE_CURRENT_TASK = ".current-task"
 
 # Only control loop for check agent
 TARGET_AGENT = "check"
@@ -49,14 +49,14 @@ def find_repo_root(start_path: str) -> str | None:
     return None
 
 
-def get_current_feature(repo_root: str) -> str | None:
-    """Read current feature directory path"""
-    current_feature_file = os.path.join(repo_root, DIR_WORKFLOW, FILE_CURRENT_FEATURE)
-    if not os.path.exists(current_feature_file):
+def get_current_task(repo_root: str) -> str | None:
+    """Read current task directory path"""
+    current_task_file = os.path.join(repo_root, DIR_WORKFLOW, FILE_CURRENT_TASK)
+    if not os.path.exists(current_task_file):
         return None
 
     try:
-        with open(current_feature_file, "r", encoding="utf-8") as f:
+        with open(current_task_file, "r", encoding="utf-8") as f:
             content = f.read().strip()
             return content if content else None
     except Exception:
@@ -149,14 +149,14 @@ def run_verify_commands(repo_root: str, commands: list[str]) -> tuple[bool, str]
     return True, "All verify commands passed"
 
 
-def get_completion_markers(repo_root: str, feature_dir: str) -> list[str]:
+def get_completion_markers(repo_root: str, task_dir: str) -> list[str]:
     """
     Read check.jsonl and generate completion markers from reasons.
 
     Each entry's "reason" field becomes {REASON}_FINISH marker.
     Example: {"file": "...", "reason": "TypeCheck"} -> "TYPECHECK_FINISH"
     """
-    check_jsonl_path = os.path.join(repo_root, feature_dir, "check.jsonl")
+    check_jsonl_path = os.path.join(repo_root, task_dir, "check.jsonl")
     markers = []
 
     if not os.path.exists(check_jsonl_path):
@@ -193,13 +193,13 @@ def load_state(repo_root: str) -> dict:
     """Load Ralph Loop state from file"""
     state_path = os.path.join(repo_root, STATE_FILE)
     if not os.path.exists(state_path):
-        return {"feature": None, "iteration": 0, "started_at": None}
+        return {"task": None, "iteration": 0, "started_at": None}
 
     try:
         with open(state_path, "r", encoding="utf-8") as f:
             return json.load(f)
     except Exception:
-        return {"feature": None, "iteration": 0, "started_at": None}
+        return {"task": None, "iteration": 0, "started_at": None}
 
 
 def save_state(repo_root: str, state: dict) -> None:
@@ -262,17 +262,17 @@ def main():
     if not repo_root:
         sys.exit(0)
 
-    # Get current feature
-    feature_dir = get_current_feature(repo_root)
-    if not feature_dir:
+    # Get current task
+    task_dir = get_current_task(repo_root)
+    if not task_dir:
         sys.exit(0)
 
     # Load state
     state = load_state(repo_root)
 
-    # Reset state if feature changed or state is too old
+    # Reset state if task changed or state is too old
     should_reset = False
-    if state.get("feature") != feature_dir:
+    if state.get("task") != task_dir:
         should_reset = True
     elif state.get("started_at"):
         try:
@@ -284,7 +284,7 @@ def main():
 
     if should_reset:
         state = {
-            "feature": feature_dir,
+            "task": task_dir,
             "iteration": 0,
             "started_at": datetime.now().isoformat(),
         }
@@ -335,7 +335,7 @@ def main():
             sys.exit(0)
     else:
         # No verify commands, fall back to completion markers
-        markers = get_completion_markers(repo_root, feature_dir)
+        markers = get_completion_markers(repo_root, task_dir)
         all_complete, missing = check_completion(agent_output, markers)
 
         if all_complete:

package/dist/templates/claude/hooks/session-start.py

@@ -5,7 +5,7 @@ Session Start Hook - Inject structured context
 Matcher: "startup" - only runs on normal startup (not resume/clear/compact)
 
 This hook injects:
-1. Current state (git status, current feature, backlog)
+1. Current state (git status, current task, task queue)
 2. Workflow guide
 3. Guidelines index (frontend/backend/guides)
 4. Session instructions (start.md)
@@ -86,21 +86,21 @@ Read and follow all instructions below carefully.
 
     print("## Frontend")
     frontend_index = read_file(
-        trellis_dir / "structure" / "frontend" / "index.md", "Not configured"
+        trellis_dir / "spec" / "frontend" / "index.md", "Not configured"
     )
     print(frontend_index)
     print()
 
     print("## Backend")
     backend_index = read_file(
-        trellis_dir / "structure" / "backend" / "index.md", "Not configured"
+        trellis_dir / "spec" / "backend" / "index.md", "Not configured"
     )
     print(backend_index)
     print()
 
     print("## Guides")
     guides_index = read_file(
-        trellis_dir / "structure" / "guides" / "index.md", "Not configured"
+        trellis_dir / "spec" / "guides" / "index.md", "Not configured"
     )
     print(guides_index)
 

package/dist/templates/cursor/commands/before-backend-dev.md

@@ -1,12 +1,12 @@
 Read the backend development guidelines before starting your development task.
 
 Execute these steps:
-1. Read `.trellis/structure/backend/index.md` to understand available guidelines
+1. Read `.trellis/spec/backend/index.md` to understand available guidelines
 2. Based on your task, read the relevant guideline files:
-   - Database work → `.trellis/structure/backend/database-guidelines.md`
-   - Error handling → `.trellis/structure/backend/error-handling.md`
-   - Logging → `.trellis/structure/backend/logging-guidelines.md`
-   - Type questions → `.trellis/structure/backend/type-safety.md`
+   - Database work → `.trellis/spec/backend/database-guidelines.md`
+   - Error handling → `.trellis/spec/backend/error-handling.md`
+   - Logging → `.trellis/spec/backend/logging-guidelines.md`
+   - Type questions → `.trellis/spec/backend/type-safety.md`
 3. Understand the coding standards and patterns you need to follow
 4. Then proceed with your development plan
 

package/dist/templates/cursor/commands/before-frontend-dev.md

@@ -1,12 +1,12 @@
 Read the frontend development guidelines before starting your development task.
 
 Execute these steps:
-1. Read `.trellis/structure/frontend/index.md` to understand available guidelines
+1. Read `.trellis/spec/frontend/index.md` to understand available guidelines
 2. Based on your task, read the relevant guideline files:
-   - Component work → `.trellis/structure/frontend/component-guidelines.md`
-   - Hook work → `.trellis/structure/frontend/hook-guidelines.md`
-   - State management → `.trellis/structure/frontend/state-management.md`
-   - Type questions → `.trellis/structure/frontend/type-safety.md`
+   - Component work → `.trellis/spec/frontend/component-guidelines.md`
+   - Hook work → `.trellis/spec/frontend/hook-guidelines.md`
+   - State management → `.trellis/spec/frontend/state-management.md`
+   - Type questions → `.trellis/spec/frontend/type-safety.md`
 3. Understand the coding standards and patterns you need to follow
 4. Then proceed with your development plan
 

package/dist/templates/cursor/commands/break-loop.md

@@ -55,8 +55,8 @@ What broader problems does this bug reveal?
 
 Solidify insights into the system:
 
-- [ ] Update `.trellis/structure/guides/` thinking guides
-- [ ] Update `.trellis/structure/backend/` or `frontend/` docs
+- [ ] Update `.trellis/spec/guides/` thinking guides
+- [ ] Update `.trellis/spec/backend/` or `frontend/` docs
 - [ ] Create issue record (if applicable)
 - [ ] Create feature ticket for root fix
 - [ ] Update check commands if needed

package/dist/templates/cursor/commands/check-backend.md

@@ -2,12 +2,12 @@ Check if the code you just wrote follows the backend development guidelines.
 
 Execute these steps:
 1. Run `git status` to see modified files
-2. Read `.trellis/structure/backend/index.md` to understand which guidelines apply
+2. Read `.trellis/spec/backend/index.md` to understand which guidelines apply
 3. Based on what you changed, read the relevant guideline files:
-   - Database changes → `.trellis/structure/backend/database-guidelines.md`
-   - Error handling → `.trellis/structure/backend/error-handling.md`
-   - Logging changes → `.trellis/structure/backend/logging-guidelines.md`
-   - Type changes → `.trellis/structure/backend/type-safety.md`
-   - Any changes → `.trellis/structure/backend/quality-guidelines.md`
+   - Database changes → `.trellis/spec/backend/database-guidelines.md`
+   - Error handling → `.trellis/spec/backend/error-handling.md`
+   - Logging changes → `.trellis/spec/backend/logging-guidelines.md`
+   - Type changes → `.trellis/spec/backend/type-safety.md`
+   - Any changes → `.trellis/spec/backend/quality-guidelines.md`
 4. Review your code against the guidelines
 5. Report any violations and fix them if found

package/dist/templates/cursor/commands/check-cross-layer.md

@@ -2,7 +2,7 @@
 
 Check if your changes considered all dimensions. Most bugs come from "didn't think of it", not lack of technical skill.
 
-> **Note**: This is a **post-implementation** safety net. Ideally, read the [Pre-Implementation Checklist](.trellis/structure/guides/pre-implementation-checklist.md) **before** writing code.
+> **Note**: This is a **post-implementation** safety net. Ideally, read the [Pre-Implementation Checklist](.trellis/spec/guides/pre-implementation-checklist.md) **before** writing code.
 
 ---
 
@@ -10,8 +10,8 @@ Check if your changes considered all dimensions. Most bugs come from "didn't thi
 
 | Document | Purpose | Timing |
 |----------|---------|--------|
-| [Pre-Implementation Checklist](.trellis/structure/guides/pre-implementation-checklist.md) | Questions before coding | **Before** writing code |
-| [Code Reuse Thinking Guide](.trellis/structure/guides/code-reuse-thinking-guide.md) | Pattern recognition | During implementation |
+| [Pre-Implementation Checklist](.trellis/spec/guides/pre-implementation-checklist.md) | Questions before coding | **Before** writing code |
+| [Code Reuse Thinking Guide](.trellis/spec/guides/code-reuse-thinking-guide.md) | Pattern recognition | During implementation |
 | **`/check-cross-layer`** (this) | Verification check | **After** implementation |
 
 ---
@@ -50,7 +50,7 @@ Based on your change type, execute relevant checks below:
 - [ ] Errors properly propagated to caller?
 - [ ] Loading/pending states handled at each layer?
 
-**Detailed Guide**: `.trellis/structure/guides/cross-layer-thinking-guide.md`
+**Detailed Guide**: `.trellis/spec/guides/cross-layer-thinking-guide.md`
 
 ---
 
@@ -73,7 +73,7 @@ Based on your change type, execute relevant checks below:
 - [ ] After modification, all usage sites updated?
 - [ ] If creating utility: Does similar utility already exist?
 
-**Detailed Guide**: `.trellis/structure/guides/code-reuse-thinking-guide.md`
+**Detailed Guide**: `.trellis/spec/guides/code-reuse-thinking-guide.md`
 
 ---
 

package/dist/templates/cursor/commands/check-frontend.md

@@ -2,12 +2,12 @@ Check if the code you just wrote follows the frontend development guidelines.
 
 Execute these steps:
 1. Run `git status` to see modified files
-2. Read `.trellis/structure/frontend/index.md` to understand which guidelines apply
+2. Read `.trellis/spec/frontend/index.md` to understand which guidelines apply
 3. Based on what you changed, read the relevant guideline files:
-   - Component changes → `.trellis/structure/frontend/component-guidelines.md`
-   - Hook changes → `.trellis/structure/frontend/hook-guidelines.md`
-   - State changes → `.trellis/structure/frontend/state-management.md`
-   - Type changes → `.trellis/structure/frontend/type-safety.md`
-   - Any changes → `.trellis/structure/frontend/quality-guidelines.md`
+   - Component changes → `.trellis/spec/frontend/component-guidelines.md`
+   - Hook changes → `.trellis/spec/frontend/hook-guidelines.md`
+   - State changes → `.trellis/spec/frontend/state-management.md`
+   - Type changes → `.trellis/spec/frontend/type-safety.md`
+   - Any changes → `.trellis/spec/frontend/quality-guidelines.md`
 4. Review your code against the guidelines
 5. Report any violations and fix them if found

package/dist/templates/cursor/commands/create-command.md

@@ -103,7 +103,7 @@ Description:
 | Session Start | `start` | `start` |
 | Pre-development | `before-` | `before-frontend-dev` |
 | Check | `check-` | `check-frontend` |
-| Record | `record-` | `record-agent-flow` |
+| Record | `record-` | `record-session` |
 | Generate | `generate-` | `generate-api-doc` |
 | Update | `update-` | `update-changelog` |
 | Other | Verb-first | `review-code`, `sync-data` |
@@ -131,10 +131,10 @@ git diff main...HEAD --name-only
 ### 2. Categorized Review
 
 **Frontend files** (`apps/web/`):
-- Reference `.trellis/structure/frontend/index.md`
+- Reference `.trellis/spec/frontend/index.md`
 
 **Backend files** (`packages/api/`):
-- Reference `.trellis/structure/backend/index.md`
+- Reference `.trellis/spec/backend/index.md`
 
 ### 3. Output Review Report
 

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

@@ -27,11 +27,11 @@ pnpm test
 ### 2. Documentation Sync
 
 **Structure Docs**:
-- [ ] Does `.trellis/structure/backend/` need updates?
+- [ ] Does `.trellis/spec/backend/` need updates?
   - New patterns, new modules, new conventions
-- [ ] Does `.trellis/structure/frontend/` need updates?
+- [ ] Does `.trellis/spec/frontend/` need updates?
   - New components, new hooks, new patterns
-- [ ] Does `.trellis/structure/guides/` need updates?
+- [ ] Does `.trellis/spec/guides/` need updates?
   - New cross-layer flows, lessons from bugs
 
 **Key Question**: 
@@ -94,7 +94,7 @@ git diff --name-only
 
 | Oversight | Consequence | Check |
 |-----------|-------------|-------|
-| Structure docs not updated | Others don't know the change | Check .trellis/structure/ |
+| Structure 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 |
@@ -106,7 +106,7 @@ git diff --name-only
 
 ```
 Development Flow:
-  Write code -> Test -> /finish-work -> git commit -> /record-agent-flow
+  Write code -> Test -> /finish-work -> git commit -> /record-session
                           |                              |
                    Ensure completeness              Record progress
                    
@@ -117,7 +117,7 @@ Debug Flow:
 ```
 
 - `/finish-work` - Check work completeness (this command)
-- `/record-agent-flow` - Record session and commits
+- `/record-session` - Record session and commits
 - `/break-loop` - Deep analysis after debugging
 
 ---

package/dist/templates/cursor/commands/integrate-skill.md

@@ -18,8 +18,8 @@ Adapt and integrate a Claude global skill into your project's development guidel
 
 > [!] **Important**: The goal of skill integration is to update **development guidelines**, not to generate project code directly.
 >
-> - Guidelines content -> Write to `.trellis/structure/{target}/doc.md`
-> - Code examples -> Place in `.trellis/structure/{target}/examples/skills/<skill-name>/`
+> - Guidelines content -> Write to `.trellis/spec/{target}/doc.md`
+> - Code examples -> Place in `.trellis/spec/{target}/examples/skills/<skill-name>/`
 > - Example files -> Use `.template` suffix (e.g., `component.tsx.template`) to avoid IDE errors
 >
 > Where `{target}` is `frontend` or `backend`, determined by skill type.
@@ -43,10 +43,10 @@ Based on skill type, determine which guidelines to update:
 
 | Skill Category | Integration Target |
 |----------------|-------------------|
-| UI/Frontend (`frontend-design`, `web-artifacts-builder`) | `.trellis/structure/frontend/` |
-| Backend/API (`mcp-builder`) | `.trellis/structure/backend/` |
+| UI/Frontend (`frontend-design`, `web-artifacts-builder`) | `.trellis/spec/frontend/` |
+| Backend/API (`mcp-builder`) | `.trellis/spec/backend/` |
 | Documentation (`doc-coauthoring`, `docx`, `pdf`) | `.trellis/` or create dedicated guidelines |
-| Testing (`webapp-testing`) | `.trellis/structure/frontend/` (E2E) |
+| Testing (`webapp-testing`) | `.trellis/spec/frontend/` (E2E) |
 
 ### 3. Analyze Skill Content
 
@@ -90,7 +90,7 @@ See `examples/skills/<skill-name>/`
 
 ```bash
 # Directory structure ({target} = frontend or backend)
-.trellis/structure/{target}/
+.trellis/spec/{target}/
 |-- doc.md                      # Add skill-related section
 |-- index.md                    # Update index
 \-- examples/
@@ -122,7 +122,7 @@ Add to the Quick Navigation table in `index.md`:
 
 ### # Overview
 - **Skill description**: [Functionality description]
-- **Integration target**: `.trellis/structure/{target}/`
+- **Integration target**: `.trellis/spec/{target}/`
 
 ### # Tech Stack Compatibility
 
@@ -134,9 +134,9 @@ Add to the Quick Navigation table in `index.md`:
 
 | Type | Path |
 |------|------|
-| Guidelines doc | `.trellis/structure/{target}/doc.md` (section: `skill-<name>`) |
-| Code examples | `.trellis/structure/{target}/examples/skills/<name>/` |
-| Index update | `.trellis/structure/{target}/index.md` |
+| Guidelines doc | `.trellis/spec/{target}/doc.md` (section: `skill-<name>`) |
+| Code examples | `.trellis/spec/{target}/examples/skills/<name>/` |
+| Index update | `.trellis/spec/{target}/index.md` |
 
 > `{target}` = `frontend` or `backend`
 
@@ -186,7 +186,7 @@ If this skill is frequently used, create a shortcut command:
 ### Directory Structure
 
 ```
-.trellis/structure/backend/
+.trellis/spec/backend/
 |-- doc.md                           # Add MCP section
 |-- index.md                         # Add index entry
 \-- examples/

package/dist/templates/cursor/commands/{onboard-developer.md → onboard.md}

@@ -41,7 +41,7 @@ Every AI session starts with a blank slate. Unlike human engineers who accumulat
 
 **The Problem**: Without memory, AI asks the same questions repeatedly, makes the same mistakes, and can't build on previous work.
 
-**The Solution**: The `.trellis/agent-traces/` system captures what happened in each session - what was done, what was learned, what problems were solved. The `/start` command reads this history at session start, giving AI "artificial memory."
+**The Solution**: The `.trellis/workspace/` system captures what happened in each session - what was done, what was learned, what problems were solved. The `/start` command reads this history at session start, giving AI "artificial memory."
 
 ### Challenge 2: AI Has Generic Knowledge, Not Project-Specific Knowledge
 
@@ -49,7 +49,7 @@ AI models are trained on millions of codebases - they know general patterns for
 
 **The Problem**: AI writes code that "works" but doesn't match your project's style. It uses patterns that conflict with existing code. It makes decisions that violate unwritten team rules.
 
-**The Solution**: The `.trellis/structure/` directory contains project-specific guidelines. The `/before-*-dev` commands inject this specialized knowledge into AI context before coding starts.
+**The Solution**: The `.trellis/spec/` directory contains project-specific guidelines. The `/before-*-dev` commands inject this specialized knowledge into AI context before coding starts.
 
 ### Challenge 3: AI Context Window Is Limited
 
@@ -66,21 +66,24 @@ Even after injecting guidelines, AI has limited context window. As conversation
 ```
 .trellis/
 |-- .developer              # Your identity (gitignored)
-|-- workflow.md                 # Complete workflow documentation
-|-- agent-traces/         # "AI Memory" - session history
+|-- workflow.md             # Complete workflow documentation
+|-- workspace/              # "AI Memory" - session history
 |   |-- index.md            # All developers' progress
 |   \-- {developer}/        # Per-developer directory
 |       |-- index.md        # Personal progress index
-|       |-- features/       # Active feature tracking
-|       \-- traces-N.md   # Session records (max 2000 lines)
-|-- structure/              # "AI Training Data" - project knowledge
+|       \-- journal-N.md    # Session records (max 2000 lines)
+|-- tasks/                  # Task tracking (unified)
+|   \-- {MM}-{DD}-{slug}/   # Task directory
+|       |-- task.json       # Task metadata
+|       \-- prd.md          # Requirements doc
+|-- spec/                   # "AI Training Data" - project knowledge
 |   |-- frontend/           # Frontend conventions
 |   |-- backend/            # Backend conventions
 |   \-- guides/             # Thinking patterns
 \-- scripts/                # Automation tools
 ```
 
-### Understanding structure/ subdirectories
+### Understanding spec/ subdirectories
 
 **frontend/** - Single-layer frontend knowledge:
 - Component patterns (how to write components in THIS project)
@@ -113,7 +116,7 @@ AI needs the same onboarding - but compressed into seconds at session start.
 **WHAT IT ACTUALLY DOES**:
 1. Reads developer identity (who am I in this project?)
 2. Checks git status (what branch? uncommitted changes?)
-3. Reads recent session history from `agent-traces/` (what happened before?)
+3. Reads recent session history from `workspace/` (what happened before?)
 4. Identifies active features (what's in progress?)
 5. Understands current project state before making any changes
 
@@ -129,7 +132,7 @@ AI needs the same onboarding - but compressed into seconds at session start.
 AI models have "pre-trained knowledge" - general patterns from millions of codebases. But YOUR project has specific conventions that differ from generic patterns.
 
 **WHAT IT ACTUALLY DOES**:
-1. Reads `.trellis/structure/frontend/` or `.trellis/structure/backend/`
+1. Reads `.trellis/spec/frontend/` or `.trellis/spec/backend/`
 2. Loads project-specific patterns into AI's working context:
    - Component naming conventions
    - State management patterns
@@ -190,13 +193,13 @@ The `/check-*` commands focus on code quality within a single layer. But real ch
 
 ---
 
-### /record-agent-flow - Persist Memory for Future
+### /record-session - Persist Memory for Future
 
 **WHY IT EXISTS**:
 All the context AI built during this session will be lost when session ends. The next session's `/start` needs this information.
 
 **WHAT IT ACTUALLY DOES**:
-1. Records session summary to `agent-traces/{developer}/traces-N.md`
+1. Records session summary to `workspace/{developer}/journal-N.md`
 2. Captures what was done, learned, and what's remaining
 3. Updates index files for quick lookup
 
@@ -207,20 +210,20 @@ All the context AI built during this session will be lost when session ends. The
 ### Example 1: Bug Fix Session
 
 **[1/8] /start** - AI needs project context before touching code
-**[2/8] ./.trellis/scripts/feature.sh create "Fix bug" --slug fix-bug** - Track work for future reference
+**[2/8] ./.trellis/scripts/task.sh create "Fix bug" --slug fix-bug** - Track work for future reference
 **[3/8] /before-frontend-dev** - Inject project-specific frontend knowledge
 **[4/8] Investigate and fix the bug** - Actual development work
 **[5/8] /check-frontend** - Re-verify code against guidelines
 **[6/8] /finish-work** - Holistic cross-layer review
 **[7/8] Human tests and commits** - Human validates before code enters repo
-**[8/8] /record-agent-flow** - Persist memory for future sessions
+**[8/8] /record-session** - Persist memory for future sessions
 
 ### Example 2: Planning Session (No Code)
 
 **[1/4] /start** - Context needed even for non-coding work
-**[2/4] ./.trellis/scripts/feature.sh create "Planning task" --slug planning-task** - Planning is valuable work
+**[2/4] ./.trellis/scripts/task.sh create "Planning task" --slug planning-task** - Planning is valuable work
 **[3/4] Review docs, create subtask list** - Actual planning work
-**[4/4] /record-agent-flow (with --summary)** - Planning decisions must be recorded
+**[4/4] /record-session (with --summary)** - Planning decisions must be recorded
 
 ### Example 3: Code Review Fixes
 
@@ -229,7 +232,7 @@ All the context AI built during this session will be lost when session ends. The
 **[3/6] Fix each CR issue** - Address feedback with guidelines in context
 **[4/6] /check-backend** - Verify fixes didn't introduce new issues
 **[5/6] /finish-work** - Document lessons from CR
-**[6/6] Human commits, then /record-agent-flow** - Preserve CR lessons
+**[6/6] Human commits, then /record-session** - Preserve CR lessons
 
 ### Example 4: Large Refactoring
 
@@ -246,7 +249,7 @@ All the context AI built during this session will be lost when session ends. The
 **[3/6] Investigation** - Actual debugging work
 **[4/6] /check-backend** - Verify debug changes don't break other things
 **[5/6] /finish-work** - Debug findings might need documentation
-**[6/6] Human commits, then /record-agent-flow** - Debug knowledge is valuable
+**[6/6] Human commits, then /record-session** - Debug knowledge is valuable
 
 ---
 
@@ -255,7 +258,7 @@ All the context AI built during this session will be lost when session ends. The
 1. **AI NEVER commits** - Human tests and approves. AI prepares, human validates.
 2. **Guidelines before code** - /before-*-dev commands inject project knowledge.
 3. **Check after code** - /check-* commands catch context drift.
-4. **Record everything** - /record-agent-flow persists memory.
+4. **Record everything** - /record-session persists memory.
 
 ---
 
@@ -265,12 +268,12 @@ After explaining Part 1 and Part 2, check if the project's development guideline
 
 ## Step 1: Check Current Guidelines Status
 
-Check if `.trellis/structure/` contains empty templates or customized guidelines:
+Check if `.trellis/spec/` contains empty templates or customized guidelines:
 
 ```bash
 # Check if files are still empty templates (look for placeholder text)
-grep -l "To be filled by the team" .trellis/structure/backend/*.md 2>/dev/null | wc -l
-grep -l "To be filled by the team" .trellis/structure/frontend/*.md 2>/dev/null | wc -l
+grep -l "To be filled by the team" .trellis/spec/backend/*.md 2>/dev/null | wc -l
+grep -l "To be filled by the team" .trellis/spec/frontend/*.md 2>/dev/null | wc -l
 ```
 
 ## Step 2: Determine Situation
@@ -281,7 +284,7 @@ If guidelines are empty templates (contain "To be filled by the team"), this is
 
 Explain to the developer:
 
-"I see that the development guidelines in `.trellis/structure/` are still empty templates. This is normal for a new Trellis setup!
+"I see that the development guidelines in `.trellis/spec/` are still empty templates. This is normal for a new Trellis setup!
 
 The templates contain placeholder text that needs to be replaced with YOUR project's actual conventions. Without this, `/before-*-dev` commands won't provide useful guidance.
 
@@ -291,7 +294,7 @@ The templates contain placeholder text that needs to be replaced with YOUR proje
 2. Identify the patterns and conventions already in use
 3. Document them in the guideline files
 
-For example, for `.trellis/structure/backend/database-guidelines.md`:
+For example, for `.trellis/spec/backend/database-guidelines.md`:
 - What ORM/query library does your project use?
 - How are migrations managed?
 - What naming conventions for tables/columns?
@@ -306,14 +309,14 @@ Explain to the developer:
 
 "Great! Your team has already customized the development guidelines. You can start using `/before-*-dev` commands right away.
 
-I recommend reading through `.trellis/structure/` to familiarize yourself with the team's coding standards."
+I recommend reading through `.trellis/spec/` to familiarize yourself with the team's coding standards."
 
 ## Step 3: Help Fill Guidelines (If Empty)
 
 If the developer wants help filling guidelines, create a feature to track this:
 
 ```bash
-./.trellis/scripts/feature.sh create "Fill structure guidelines" --slug fill-structure-guidelines
+./.trellis/scripts/task.sh create "Fill structure guidelines" --slug fill-structure-guidelines
 ```
 
 Then systematically analyze the codebase and fill each guideline file:
@@ -348,8 +351,8 @@ After covering all three parts, summarize:
 - Part 3: Guidelines status (empty templates need filling / already customized)
 
 **Next steps** (tell user):
-1. Run `/record-agent-flow` to record this onboard session
-2. [If guidelines empty] Start filling in `.trellis/structure/` guidelines
+1. Run `/record-session` to record this onboard session
+2. [If guidelines empty] Start filling in `.trellis/spec/` guidelines
 3. [If guidelines ready] Start your first development task
 
 What would you like to do first?"

package/dist/templates/cursor/commands/{record-agent-flow.md → record-session.md}

@@ -35,18 +35,18 @@ EOF
 ```
 
 **Auto-completes**:
-- [OK] Appends session to traces-N.md
+- [OK] Appends session to journal-N.md
 - [OK] Auto-detects line count, creates new file if >2000 lines
 - [OK] Updates index.md (Total Sessions +1, Last Active, line stats, history)
 
 ---
 
-## Archive Completed Feature (if any)
+## Archive Completed Task (if any)
 
-If a feature was completed this session:
+If a task was completed this session:
 
 ```bash
-./.trellis/scripts/feature.sh archive <feature-name>
+./.trellis/scripts/task.sh archive <task-name>
 ```
 
 ---
@@ -57,6 +57,6 @@ If a feature was completed this session:
 |---------|---------|
 | `get-context.sh` | Get all context info |
 | `add-session.sh --title "..." --commit "..."` | **One-click add session (recommended)** |
-| `feature.sh create "<title>" [--slug <name>]` | Create new feature directory |
-| `feature.sh archive <name>` | Archive completed feature |
-| `feature.sh list` | List active features |
+| `task.sh create "<title>" [--slug <name>]` | Create new task directory |
+| `task.sh archive <name>` | Archive completed task |
+| `task.sh list` | List active tasks |