steerdev 0.5.4__tar.gz → 0.5.6__tar.gz

{steerdev-0.5.4 → steerdev-0.5.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: steerdev
-Version: 0.5.4
+Version: 0.5.6
 Summary: Backend task runner for steerdev.com - orchestrates CLI coding agents with activity reporting
 Project-URL: Homepage, https://github.com/pentoai/steerdev-agent
 Project-URL: Repository, https://github.com/pentoai/steerdev-agent

{steerdev-0.5.4 → steerdev-0.5.6}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "steerdev"
-version = "0.5.4"
+version = "0.5.6"
 description = "Backend task runner for steerdev.com - orchestrates CLI coding agents with activity reporting"
 readme = "README.md"
 authors = [

{steerdev-0.5.4 → steerdev-0.5.6}/src/steerdev_agent/setup/templates/claude_md_section.md

@@ -30,14 +30,31 @@ BACKLOG → TODO → IN-PROGRESS → DONE
 
 ### Workflow
 
+#### Standard Mode (one task at a time)
+
 1. Run `steerdev tasks next` to get the next task
 2. Update task to `in-progress` before starting work
-3. **Create a feature branch** using the task ID: `git checkout -b task/<task-id-short>`
+3. **Create a feature branch**: `git checkout -b task/<task-id-short>`
 4. Implement the task
 5. **Commit your changes** with clear, descriptive commit messages
-6. **Create a pull request** using GitHub CLI: `gh pr create`
+6. **Push and create a pull request**: `git push -u origin HEAD && gh pr create`
 7. Update task to `done` with a result summary and PR URL: `--result "Summary of work done. PR: <url>"`
 
+#### Wave Mode (multiple tasks in one session)
+
+When your prompt includes a **"Wave Context"** section, you are in wave mode. One branch and one PR cover the entire wave.
+
+1. **Create a wave branch once**: `git checkout -b wave/<wave-number>` (e.g. `wave/1`)
+2. For **each task** in the wave:
+   a. Update task to `in-progress`
+   b. Implement the task
+   c. **Commit** with a message that references the task: `[task:<id>] feat: ...`
+   d. Update task to `done` with a result summary (no PR yet)
+3. After **all tasks** are complete:
+   a. `git push -u origin HEAD`
+   b. Create a **single PR** for the wave (title: `Wave <N>: <description>`, body lists all completed tasks)
+   c. Update all tasks with the PR URL
+
 ### Git Workflow (Required)
 
 **You MUST use Git and GitHub CLI to manage your work.** Every task implementation must result in a pull request.
@@ -47,11 +64,13 @@ BACKLOG → TODO → IN-PROGRESS → DONE
 Create a branch before starting any implementation work:
 
 ```bash
-# Use task ID for branch name (use first 8 chars of UUID)
+# Standard mode: use task ID (first 8 chars of UUID)
 git checkout -b task/<short-task-id>
+# Example: git checkout -b task/abc12345
 
-# Example
-git checkout -b task/abc12345
+# Wave mode: use wave number
+git checkout -b wave/<wave-number>
+# Example: git checkout -b wave/1
 ```
 
 #### Committing Changes
@@ -78,10 +97,9 @@ Follow conventional commit format:
 
 #### Creating Pull Requests
 
-**Always create a PR when completing a task:**
+##### Standard Mode PR (per task)
 
 ```bash
-# Push branch and create PR
 git push -u origin HEAD
 gh pr create --title "Task: <title>" --body "## Summary
 
@@ -98,7 +116,29 @@ Task ID: <task-id>
 - How to test the changes"
 ```
 
-#### Complete Workflow Example
+##### Wave Mode PR (per wave)
+
+After all wave tasks are complete, create a single PR:
+
+```bash
+git push -u origin HEAD
+gh pr create --title "Wave <N>: <brief description>" --body "## Summary
+
+Wave <N> implementation covering <number> tasks.
+
+## Tasks Completed
+- [task:<id1>] <title1>
+- [task:<id2>] <title2>
+
+## Changes Made
+- Change 1
+- Change 2
+
+## Testing
+- How to test the changes"
+```
+
+#### Standard Workflow Example
 
 ```bash
 # 1. Get next task
@@ -122,9 +162,38 @@ gh pr create --title "Add user data endpoint" --body "Implementation for task ab
 steerdev tasks update abc123-... --status done --result "Implemented user data endpoint. PR: https://github.com/org/repo/pull/42"
 ```
 
-**IMPORTANT:** Never leave work uncommitted. Always create a PR before marking a task as `done`.
+#### Wave Workflow Example
+
+```bash
+# 1. Create wave branch (once for the entire wave)
+git checkout -b wave/1
+
+# 2. First task
+steerdev tasks update task-aaa... --status in-progress
+# ... implement ...
+git add . && git commit -m "[task:task-aaa] feat: add user endpoint"
+steerdev tasks update task-aaa... --status done --result "Added user endpoint"
+
+# 3. Second task (same branch)
+steerdev tasks update task-bbb... --status in-progress
+# ... implement ...
+git add . && git commit -m "[task:task-bbb] fix: validate email format"
+steerdev tasks update task-bbb... --status done --result "Fixed email validation"
+
+# 4. All tasks done — push and create single PR
+git push -u origin HEAD
+gh pr create --title "Wave 1: User management improvements" \
+  --body "## Tasks Completed
+- [task:task-aaa] Add user endpoint
+- [task:task-bbb] Fix email validation"
+# Returns: https://github.com/org/repo/pull/42
+
+# 5. Update all tasks with PR URL
+steerdev tasks update task-aaa... --result "PR: https://github.com/org/repo/pull/42"
+steerdev tasks update task-bbb... --result "PR: https://github.com/org/repo/pull/42"
+```
 
-**Wave Mode:** If you are running in **wave mode** (processing multiple tasks in a single session), **only create the PR at the end of the wave**, not after each individual task. Commit your changes after each task, but defer the `git push` and PR creation until all tasks in the wave are completed.
+**IMPORTANT:** Never leave work uncommitted. Always create a PR before marking a task as `done`.
 
 ### Status Values
 

{steerdev-0.5.4 → steerdev-0.5.6}/src/steerdev_agent/setup/templates/skills/git-workflow/SKILL.md

@@ -10,7 +10,7 @@ This skill provides Git workflow commands with steerdev conventions for branch m
 
 ## Available Commands
 
-### Create Task Branch
+### Create Task Branch (Standard Mode)
 
 ```bash
 steerdev git branch TASK_ID [--name NAME]
@@ -39,6 +39,22 @@ steerdev git branch abc12345-def6-7890-... --name auth-flow
 - If branch already exists, switches to it
 - If branch doesn't exist, creates and switches to it
 
+### Create Wave Branch (Wave Mode)
+
+In wave mode, create a single branch for the entire wave instead of per-task branches:
+
+```bash
+git checkout -b wave/<wave-number>
+
+# Example
+git checkout -b wave/1
+```
+
+**Behavior:**
+- Create the wave branch **once** at the start of the wave
+- All tasks in the wave are committed to this branch
+- Do not create per-task branches in wave mode
+
 ### Create Pull Request
 
 ```bash
@@ -53,7 +69,8 @@ Create a pull request using GitHub CLI with steerdev conventions.
 - `--task-id`: Task ID to reference in PR
 - `--draft`, `-d`: Create as draft PR
 
-**Examples:**
+#### Standard Mode PR (per task)
+
 ```bash
 # Simple PR
 steerdev git pr --title "Add user authentication"
@@ -80,6 +97,29 @@ steerdev git pr \
   --draft
 ```
 
+#### Wave Mode PR (per wave)
+
+After all wave tasks are complete, create a single PR:
+
+```bash
+steerdev git pr \
+  --title "Wave <N>: <brief description>" \
+  --body "## Summary
+
+Wave <N> implementation covering <number> tasks.
+
+## Tasks Completed
+- [task:<id1>] <title1>
+- [task:<id2>] <title2>
+
+## Changes Made
+- Change 1
+- Change 2
+
+## Testing
+- How to test the changes"
+```
+
 **Note:** Requires GitHub CLI (`gh`) to be installed and authenticated.
 
 ### Check Git Status
@@ -109,6 +149,8 @@ Status: 2 ahead, 0 behind
 
 ## Complete Workflow Example
 
+### Standard Workflow Example
+
 ```bash
 # 1. Get next task
 steerdev tasks next
@@ -175,9 +217,65 @@ steerdev tasks update abc12345... \
   --result "Implemented auth. PR: https://github.com/org/repo/pull/42"
 ```
 
+### Wave Workflow Example
+
+```bash
+# 1. Create wave branch (once for the entire wave)
+git checkout -b wave/1
+
+# --- Task 1 ---
+steerdev tasks update task-aaa... --status started
+
+# Create progress log
+TIMESTAMP=$(date -u +%Y%m%d_%H%M%S)
+DOC_FILE="docs/${TIMESTAMP}_wave_1.md"
+echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","task_id":"task-aaa","event":"started","message":"Wave 1: starting task 1"}' >> docs/progress.jsonl
+
+# ... implement task 1 ...
+git add .
+git commit -m "[task:task-aaa] feat: add user endpoint"
+steerdev tasks update task-aaa... --status completed \
+  --result "Added user endpoint"
+
+# --- Task 2 ---
+steerdev tasks update task-bbb... --status started
+echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","task_id":"task-bbb","event":"started","message":"Wave 1: starting task 2"}' >> docs/progress.jsonl
+
+# ... implement task 2 ...
+git add .
+git commit -m "[task:task-bbb] fix: validate email format"
+steerdev tasks update task-bbb... --status completed \
+  --result "Fixed email validation"
+
+# --- All tasks done — push and create single PR ---
+git push -u origin HEAD
+steerdev git pr \
+  --title "Wave 1: User management improvements" \
+  --body "## Summary
+
+Wave 1 implementation covering 2 tasks.
+
+## Tasks Completed
+- [task:task-aaa] Add user endpoint
+- [task:task-bbb] Fix email validation
+
+## Changes Made
+- New user CRUD endpoint
+- Email format validation on signup
+
+## Testing
+- Run \`npm test\` to verify"
+# Returns: https://github.com/org/repo/pull/42
+
+# Log completion and update all tasks with PR URL
+echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","task_id":"wave-1","event":"completed","message":"Wave 1 complete","pr_url":"https://github.com/org/repo/pull/42"}' >> docs/progress.jsonl
+steerdev tasks update task-aaa... --result "PR: https://github.com/org/repo/pull/42"
+steerdev tasks update task-bbb... --result "PR: https://github.com/org/repo/pull/42"
+```
+
 ## Branch Naming Convention
 
-Branches follow the pattern: `task/<short-task-id>[-optional-suffix]`
+**Standard mode** — branches follow the pattern: `task/<short-task-id>[-optional-suffix]`
 
 - `task/abc12345` - Basic task branch
 - `task/abc12345-auth` - With descriptive suffix
@@ -185,6 +283,11 @@ Branches follow the pattern: `task/<short-task-id>[-optional-suffix]`
 
 The short task ID is the first 8 characters of the full UUID.
 
+**Wave mode** — branches follow the pattern: `wave/<wave-number>`
+
+- `wave/1` - First wave
+- `wave/2` - Second wave
+
 ## PR Conventions
 
 Pull requests created via this skill include:
@@ -197,16 +300,21 @@ Pull requests created via this skill include:
 
 ## Important Rules
 
-1. **Always create a branch** before starting work
+**Always:**
+1. **Create a branch** before starting work
 2. **Commit frequently** with descriptive messages
-3. **Create PR before marking task complete**
-4. **Include PR URL** in task completion result
-5. **Log progress** to `docs/progress.jsonl` (see Progress Logging skill)
-6. **Log completion** with PR URL before marking task done
-
-## Wave Mode
-
-If you are running in **wave mode** (processing multiple tasks in a single session), **only create the PR at the end of the wave**, not after each individual task. Commit your changes after each task, but defer the `git push` and `gh pr create` until all tasks in the wave are completed. The PR should then reference all tasks completed in the wave.
+3. **Log progress** to `docs/progress.jsonl` (see Progress Logging skill)
+4. **Log completion** with PR URL before marking task done
+
+**Standard mode:**
+5. **Create a PR per task** before marking it as `completed`
+6. **Include PR URL** in the task result summary
+
+**Wave mode:**
+5. **One branch per wave** (`wave/<N>`) — do not create per-task branches
+6. **Commit per task** with `[task:<id>]` prefix for traceability
+7. **One PR per wave** — defer `git push` and `gh pr create` until all wave tasks are done
+8. **Update all tasks** with the wave PR URL after creating the PR
 
 ## Prerequisites
 

{steerdev-0.5.4 → steerdev-0.5.6}/src/steerdev_agent/setup/templates/skills/task-management/SKILL.md

@@ -110,6 +110,8 @@ Create a new task for discovered work items.
 
 ## Workflow
 
+### Standard Mode (one task at a time)
+
 1. **On start**: Run `steerdev tasks next` to get the next task
 2. **Update task** to `started` before starting work
 3. **Create progress log**: Create `docs/{timestamp}_{task_slug}.md` and log `started` event to `docs/progress.jsonl`
@@ -122,6 +124,25 @@ Create a new task for discovered work items.
 10. **Update task** to `completed` with a result summary and PR URL
 11. **Fetch next task** and repeat
 
+### Wave Mode (multiple tasks in one session)
+
+When your prompt includes a **"Wave Context"** section, you are in wave mode. One branch and one PR cover the entire wave.
+
+1. **Create a wave branch once**: `git checkout -b wave/<wave-number>` (e.g. `wave/1`)
+2. For **each task** in the wave:
+   a. Run `steerdev tasks next` (or pick the next task from the wave context)
+   b. **Update task** to `started`
+   c. **Create progress log** and log `started` event
+   d. **Implement** the task
+   e. **Verify visually** if applicable
+   f. **Commit** with a message referencing the task: `[task:<id>] feat: ...`
+   g. **Update task** to `completed` with a result summary (no PR yet)
+3. After **all wave tasks** are complete:
+   a. `git push -u origin HEAD`
+   b. Create a **single PR** for the wave (title: `Wave <N>: <description>`, body lists all completed tasks)
+   c. **Log completion** with PR URL
+   d. **Update all tasks** with the PR URL
+
 **IMPORTANT**: Always write progress logs. See the Progress Logging skill for details.
 
 ## Visual Verification for Web Changes (Required)
@@ -216,11 +237,13 @@ When creating pull requests for visual changes, mention that screenshots were ta
 Create a branch before starting any implementation work:
 
 ```bash
-# Use task ID for branch name (use first 8 chars of UUID)
+# Standard mode: use task ID (first 8 chars of UUID)
 git checkout -b task/<short-task-id>
+# Example: git checkout -b task/abc12345
 
-# Example
-git checkout -b task/abc12345
+# Wave mode: use wave number
+git checkout -b wave/<wave-number>
+# Example: git checkout -b wave/1
 ```
 
 ### Committing Changes
@@ -228,9 +251,18 @@ git checkout -b task/abc12345
 Make atomic commits with clear, descriptive messages:
 
 ```bash
+# Standard mode
 git add .
 git commit -m "feat: implement user authentication
 
+- Add JWT token generation
+- Create login/logout endpoints
+- Add auth middleware"
+
+# Wave mode — prefix with [task:<id>] for traceability
+git add .
+git commit -m "[task:abc12345] feat: implement user authentication
+
 - Add JWT token generation
 - Create login/logout endpoints
 - Add auth middleware"
@@ -246,10 +278,9 @@ Follow conventional commit format:
 
 ### Creating Pull Requests
 
-**Always create a PR when completing a task:**
+#### Standard Mode PR (per task)
 
 ```bash
-# Push branch and create PR
 git push -u origin HEAD
 gh pr create --title "Task: <title>" --body "## Summary
 
@@ -266,19 +297,49 @@ Task ID: <task-id>
 - How to test the changes"
 ```
 
+#### Wave Mode PR (per wave)
+
+After all wave tasks are complete, create a single PR:
+
+```bash
+git push -u origin HEAD
+gh pr create --title "Wave <N>: <brief description>" --body "## Summary
+
+Wave <N> implementation covering <number> tasks.
+
+## Tasks Completed
+- [task:<id1>] <title1>
+- [task:<id2>] <title2>
+
+## Changes Made
+- Change 1
+- Change 2
+
+## Testing
+- How to test the changes"
+```
+
 ### Important Rules
 
-- **Never leave work uncommitted** - Always commit before stopping work
-- **Always create a PR** before marking a task as `completed`
-- **Include PR URL** in the task result summary
+**Always:**
+- **Never leave work uncommitted** — always commit before stopping work
 - **Use descriptive commit messages** that explain the "why" not just the "what"
+- **Log progress** to `docs/progress.jsonl`
 
-### Wave Mode
+**Standard mode:**
+- **Create a PR per task** before marking it as `completed`
+- **Include PR URL** in the task result summary
 
-If you are running in **wave mode** (processing multiple tasks in a single session), **only create the PR at the end of the wave**, not after each individual task. Commit your changes after each task, but defer the `git push` and `gh pr create` until all tasks in the wave are completed. The PR should then reference all tasks completed in the wave.
+**Wave mode:**
+- **One branch per wave** (`wave/<N>`) — do not create per-task branches
+- **Commit per task** with `[task:<id>]` prefix for traceability
+- **One PR per wave** — defer `git push` and `gh pr create` until all wave tasks are done
+- **Update all tasks** with the wave PR URL after creating the PR
 
 ## Example Session
 
+### Standard Mode Example
+
 ```bash
 # Get next task
 steerdev tasks next
@@ -325,6 +386,52 @@ steerdev tasks update abc123-... --status completed \
 steerdev tasks next
 ```
 
+### Wave Mode Example
+
+```bash
+# 1. Create wave branch (once for the entire wave)
+git checkout -b wave/1
+
+# --- Task 1 ---
+steerdev tasks update task-aaa... --status started
+# ... implement task 1 ...
+git add .
+git commit -m "[task:task-aaa] feat: add user endpoint"
+steerdev tasks update task-aaa... --status completed \
+  --result "Added user endpoint"
+
+# --- Task 2 ---
+steerdev tasks update task-bbb... --status started
+# ... implement task 2 ...
+git add .
+git commit -m "[task:task-bbb] fix: validate email format"
+steerdev tasks update task-bbb... --status completed \
+  --result "Fixed email validation"
+
+# --- All tasks done — create single PR ---
+git push -u origin HEAD
+gh pr create --title "Wave 1: User management improvements" \
+  --body "## Summary
+
+Wave 1 implementation covering 2 tasks.
+
+## Tasks Completed
+- [task:task-aaa] Add user endpoint
+- [task:task-bbb] Fix email validation
+
+## Changes Made
+- New user CRUD endpoint
+- Email format validation on signup
+
+## Testing
+- Run \`npm test\` to verify"
+# Returns: https://github.com/org/repo/pull/42
+
+# Update all tasks with PR URL
+steerdev tasks update task-aaa... --result "PR: https://github.com/org/repo/pull/42"
+steerdev tasks update task-bbb... --result "PR: https://github.com/org/repo/pull/42"
+```
+
 ## Adding Comments
 
 You can add markdown comments to tasks at any time:

{steerdev-0.5.4 → steerdev-0.5.6}/src/steerdev_agent/version.py

@@ -5,6 +5,7 @@ Provides functions to get and manage the project version from pyproject.toml.
 
 import subprocess
 import tomllib
+from importlib.metadata import PackageNotFoundError, version
 from pathlib import Path
 
 
@@ -14,14 +15,23 @@ def get_project_root() -> Path:
 
 
 def get_version() -> str:
-    """Get the current project version from pyproject.toml.
+    """Get the current project version.
 
-    First tries to use `uv version --short`, then falls back to reading
-    pyproject.toml directly.
+    Resolution order:
+    1. Installed package metadata (works when installed via pip/uv)
+    2. `uv version --short` (works in dev with uv)
+    3. Read pyproject.toml directly (works in dev without uv)
 
     Returns:
-        The current version string (e.g., "0.1.0")
+        The current version string (e.g., "0.5.4")
     """
+    # 1. Try installed package metadata (always works for installed packages)
+    try:
+        return version("steerdev")
+    except PackageNotFoundError:
+        pass
+
+    # 2. Try uv (dev environment)
     try:
         result = subprocess.run(
             ["uv", "version", "--short"],
@@ -32,13 +42,15 @@ def get_version() -> str:
         )
         return result.stdout.strip()
     except (subprocess.CalledProcessError, FileNotFoundError):
-        # Fallback: read directly from pyproject.toml
-        pyproject_path = get_project_root() / "pyproject.toml"
-        if pyproject_path.exists():
-            with open(pyproject_path, "rb") as f:
-                data = tomllib.load(f)
-                return data.get("project", {}).get("version", "unknown")
-        return "unknown"
+        pass
+
+    # 3. Fallback: read directly from pyproject.toml (dev environment)
+    pyproject_path = get_project_root() / "pyproject.toml"
+    if pyproject_path.exists():
+        with open(pyproject_path, "rb") as f:
+            data = tomllib.load(f)
+            return data.get("project", {}).get("version", "unknown")
+    return "unknown"
 
 
 def bump_version(