@johndaskovsky/nightshift 0.1.0

package/templates/commands/nightshift-add-task.md

@@ -0,0 +1,96 @@
+---
+description: Add a task to an existing Nightshift shift
+---
+
+Add a new task file to a shift and update the table with a corresponding status column.
+
+**Input**: The argument after `/nightshift-add-task` is the shift name, or omit to select interactively.
+
+**Steps**
+
+1. **Select the shift**
+
+   If a name is provided, use it. Otherwise:
+   - List directories in `.nightshift/` (excluding `archive/`)
+   - If no shifts exist, report: "No active shifts. Use `/nightshift-create` first."
+   - If one shift exists, auto-select it
+   - If multiple shifts exist, use the **AskUserQuestion tool** to let the user pick
+
+2. **Get task details**
+
+   Use the **AskUserQuestion tool** (open-ended) to ask:
+   > "Describe this task. What should the agent do for each item? Include the tools needed, step-by-step instructions, and how to verify success."
+
+   From their description, derive:
+   - A kebab-case task name
+   - The Configuration section (tools list)
+   - The Steps section (numbered instructions)
+   - The Validation section (verification criteria)
+
+3. **Check for task name conflicts**
+
+   If a file `<task-name>.md` already exists in the shift directory, report the conflict and suggest a different name.
+
+4. **Create the task file**
+
+   Write `.nightshift/<shift-name>/<task-name>.md`:
+
+   ```markdown
+   ## Configuration
+
+   - tools: <tool1>, <tool2>
+
+   ## Steps
+
+   1. <step description>
+   2. <step description>
+   3. <step description>
+
+   ## Validation
+
+   - <criterion 1>
+   - <criterion 2>
+   ```
+
+5. **Update table.csv**
+
+   Read `table.csv` and add a new column for this task:
+   - Column header: the task name (e.g., `create-page`)
+   - All existing rows get status `todo` in this column
+   - If the table is empty (header only), just add the column header
+
+6. **Update manager.md**
+
+   Add the task to the `## Task Order` section:
+   - If it's the first task, replace the placeholder text with `1. <task-name>`
+   - Otherwise, append as the next numbered item
+
+7. **Show result**
+
+   Present the created task file for review and show the updated state:
+
+   ```
+   ## Task Added: <task-name>
+
+   **Shift:** <shift-name>
+   **File:** `.nightshift/<shift-name>/<task-name>.md`
+
+   ### Configuration
+   - tools: <tools>
+
+   ### Steps
+   1. ...
+
+   ### Validation
+   - ...
+
+   Table updated: <N> items now have `<task-name>: todo`
+   Manager updated: task order now includes `<task-name>`
+   ```
+
+**Guardrails**
+- Always create all three sections (Configuration, Steps, Validation)
+- Initialize all existing table rows with `todo` for the new task column
+- Update manager.md task order to include the new task
+- Validate kebab-case task naming
+- Never overwrite an existing task file

package/templates/commands/nightshift-archive.md

@@ -0,0 +1,67 @@
+---
+description: Archive a completed Nightshift shift
+---
+
+Move a completed (or partially completed) shift to the archive directory with a date prefix.
+
+**Input**: The argument after `/nightshift-archive` is the shift name, or omit to select interactively.
+
+**Steps**
+
+1. **Select the shift**
+
+   If a name is provided, use it. Otherwise:
+   - List directories in `.nightshift/` (excluding `archive/`)
+   - If no shifts exist, report: "No active shifts to archive."
+   - If one shift exists, auto-select it
+   - If multiple shifts exist, use the **AskUserQuestion tool** to let the user pick
+
+2. **Validate the shift exists**
+
+   Check `.nightshift/<name>/` exists. If not, report the error.
+
+3. **Check for incomplete items**
+
+   Read `table.csv` and check for items NOT in `done` status:
+   - If incomplete items exist, warn:
+     ```
+     Warning: Shift has incomplete items:
+     - X items with status "todo"
+     - Y items with status "failed"
+     - Z items with status "in_progress"
+     ```
+     Use the **AskUserQuestion tool** to confirm:
+     > "Archive anyway?"
+     Options: "Yes, archive with incomplete items" / "No, cancel"
+
+   - If user cancels, STOP
+
+4. **Check for archive name collision**
+
+   The target is `.nightshift/archive/YYYY-MM-DD-<name>/` using today's date.
+   - If the target already exists, report: "Archive target already exists: `.nightshift/archive/YYYY-MM-DD-<name>/`. Cannot overwrite."
+   - STOP if collision found
+
+5. **Move to archive**
+
+   Use bash to move the shift directory:
+   ```bash
+   mv .nightshift/<name> .nightshift/archive/YYYY-MM-DD-<name>
+   ```
+
+6. **Confirm**
+
+   ```
+   ## Shift Archived
+
+   **Shift:** <name>
+   **Location:** `.nightshift/archive/YYYY-MM-DD-<name>/`
+
+   All files preserved (manager.md, table.csv, task files).
+   ```
+
+**Guardrails**
+- Always use today's date in ISO YYYY-MM-DD format for the archive prefix
+- Never overwrite an existing archive
+- Warn about incomplete items but allow archiving with confirmation
+- Preserve all files in the move (manager.md, table.csv, all task .md files)

package/templates/commands/nightshift-create.md

@@ -0,0 +1,85 @@
+---
+description: Create a new Nightshift shift with manager, table, and optional task files
+---
+
+Create a new Nightshift shift — a structured unit of batch agent work.
+
+**Input**: The argument after `/nightshift-create` is the shift name (kebab-case), or omit for interactive mode.
+
+**Steps**
+
+1. **Get shift name**
+
+   If a name is provided as argument, use it. Otherwise, use the **AskUserQuestion tool** (open-ended) to ask:
+   > "What will this shift do? Describe the batch work and I'll derive a name."
+
+   Derive a kebab-case name from their description (e.g., "create promo example pages" -> `create-promo-examples`).
+
+2. **Validate the name**
+
+   - Must be kebab-case: lowercase letters, numbers, and hyphens only
+   - If invalid, report the error and ask for a valid name
+
+3. **Check for conflicts**
+
+   - If `.nightshift/<name>/` already exists, report: "Shift `<name>` already exists. Use `/nightshift-start <name>` to resume it."
+   - STOP if conflict found
+
+4. **Create the shift directory and files**
+
+   Create `.nightshift/<name>/` with these files:
+
+   **manager.md:**
+   ```markdown
+   ## Shift Configuration
+
+   - name: <name>
+   - created: <YYYY-MM-DD>
+
+   ## Task Order
+
+   (no tasks yet — use `/nightshift-add-task <name>` to add tasks)
+
+   ## Progress
+
+   - Total items: 0
+   - Completed: 0
+   - Failed: 0
+   - Remaining: 0
+   ```
+
+   **table.csv:**
+   ```
+   row
+   ```
+
+   (Just the header row with the `row` column — items and task columns added later.)
+
+5. **Ask about initial tasks**
+
+   Use the **AskUserQuestion tool** to ask:
+   > "Shift `<name>` created! Do you want to add a task now?"
+
+   Options: "Yes, add a task" / "No, I'll add tasks later"
+
+   If yes, guide them through `/nightshift-add-task <name>` flow (describe the task, create the file, update table and manager).
+
+**Output**
+
+```
+## Shift Created: <name>
+
+**Location:** `.nightshift/<name>/`
+**Files:** manager.md, table.csv
+
+### Next Steps
+- `/nightshift-add-task <name>` — add tasks to the shift
+- `/nightshift-update-table <name>` — add items to the table
+- `/nightshift-start <name>` — begin execution (after adding tasks and items)
+```
+
+**Guardrails**
+- Always validate kebab-case naming
+- Never overwrite an existing shift
+- Create both manager.md and table.csv even if no tasks or items are defined yet
+- Use today's date (ISO YYYY-MM-DD) for the created field

package/templates/commands/nightshift-start.md

@@ -0,0 +1,78 @@
+---
+description: Start or resume execution of a Nightshift shift
+---
+
+Begin or resume executing a Nightshift shift by invoking the manager agent.
+
+**Input**: The argument after `/nightshift-start` is the shift name, or omit to select interactively.
+
+**Steps**
+
+1. **Select the shift**
+
+   If a name is provided, use it. Otherwise:
+   - List directories in `.nightshift/` (excluding `archive/`)
+   - If no shifts exist, report: "No active shifts. Use `/nightshift-create` to create one."
+   - If one shift exists, auto-select it
+   - If multiple shifts exist, use the **AskUserQuestion tool** to let the user pick
+
+2. **Validate the shift exists**
+
+   - Check `.nightshift/<name>/` exists
+   - Check `manager.md` and `table.csv` exist within it
+   - If missing, report the error and suggest `/nightshift-create`
+
+3. **Check if shift is already complete**
+
+   Read `table.csv` and check if ALL item-task statuses are `done`:
+   - If complete: report "Shift `<name>` is already complete! All items are done." and suggest `/nightshift-archive <name>`
+   - If no items exist (table has only header): report "Shift has no items. Use `/nightshift-update-table <name>` to add items first."
+   - If no task columns exist: report "Shift has no tasks. Use `/nightshift-add-task <name>` to add tasks first."
+
+4. **Show pre-flight summary**
+
+   Read `manager.md` and `table.csv` to display:
+   ```
+   ## Starting Shift: <name>
+
+   **Tasks:** <task-1>, <task-2>, ...
+   **Items:** N total
+   **Status:** X done, Y failed, Z remaining
+
+   Beginning execution...
+   ```
+
+5. **Invoke the manager agent**
+
+   Use the **Task tool** to invoke the `nightshift-manager` subagent with:
+   ```
+   Execute Nightshift shift "<name>".
+
+   Shift directory: .nightshift/<name>/
+
+   Read manager.md for task order and configuration.
+   Read table.csv for item statuses.
+   Process all remaining items following the orchestration logic in your instructions.
+   ```
+
+6. **Report results**
+
+   After the manager completes, display the final status:
+   ```
+   ## Shift Execution Complete
+
+   **Shift:** <name>
+   **Completed:** N
+   **Failed:** N
+   **Remaining:** N
+
+   [If all done] All items complete! Archive with `/nightshift-archive <name>`
+   [If failures] Some items failed. Review table.csv for details.
+   [If remaining] Shift paused. Resume with `/nightshift-start <name>`
+   ```
+
+**Guardrails**
+- Always validate the shift directory structure before starting
+- Show the pre-flight summary before invoking the manager
+- Report results after the manager finishes
+- Don't invoke the manager if there's nothing to process

package/templates/commands/nightshift-test-task.md

@@ -0,0 +1,88 @@
+---
+description: Run a single Nightshift task on a single table row for testing
+---
+
+Execute a single task on one item for testing purposes — without modifying the table state.
+
+**Input**: The argument after `/nightshift-test-task` is the shift name, or omit to select interactively.
+
+**Steps**
+
+1. **Select the shift**
+
+   If a name is provided, use it. Otherwise:
+   - List directories in `.nightshift/` (excluding `archive/`)
+   - Auto-select if only one exists, otherwise prompt for selection
+
+2. **Select the task**
+
+   List task files (`.md` files excluding `manager.md`) in the shift directory.
+   - If one task exists, auto-select it
+   - If multiple tasks exist, use the **AskUserQuestion tool** to let the user pick
+
+3. **Select the row**
+
+   Read `table.csv` and show available rows. Use the **AskUserQuestion tool** to ask:
+   > "Which row do you want to test? Enter a row number."
+
+   Show a preview of the row's metadata columns to help them choose.
+
+4. **Execute the task (dev agent)**
+
+   Use the **Task tool** to invoke the `nightshift-dev` subagent with:
+   ```
+   You are executing Nightshift task "<task-name>" on a single item FOR TESTING.
+   Do NOT modify table.csv or manager.md.
+
+   ## Shift Directory
+   .nightshift/<shift-name>/
+
+   ## Task File
+   <full contents of task-name.md>
+
+   ## Item Data (Row <N>)
+   <all column values for this row>
+
+   Execute the steps and return structured results.
+   ```
+
+5. **Verify the task (qa agent)**
+
+   Use the **Task tool** to invoke the `nightshift-qa` subagent with:
+   ```
+   You are verifying Nightshift task "<task-name>" on a single item FOR TESTING.
+
+   ## Task Validation Criteria
+   <Validation section from task file>
+
+   ## Item Data (Row <N>)
+   <all column values>
+
+   ## Dev Results
+   <dev agent's returned results>
+
+   Check each criterion and return structured results.
+   ```
+
+6. **Display results (without updating table)**
+
+   ```
+   ## Test Results: <task-name> on Row <N>
+
+   ### Dev Execution
+   <step-by-step results from dev agent>
+
+   ### QA Verification
+   <per-criterion results from qa agent>
+
+   ### Overall: PASS / FAIL
+
+   Note: Table state was NOT modified. This was a test run only.
+   ```
+
+**Guardrails**
+- NEVER modify table.csv during a test run
+- NEVER modify manager.md during a test run
+- Always run both dev and qa agents to get the full picture
+- Display detailed results so the user can debug task definitions
+- Include the "test run only" note in output

package/templates/commands/nightshift-update-table.md

@@ -0,0 +1,81 @@
+---
+description: Make bulk changes to a Nightshift shift table
+---
+
+Bulk modify the table.csv of a shift — add rows, update metadata, or reset failed items.
+
+**Input**: The argument after `/nightshift-update-table` is the shift name, or omit to select interactively.
+
+**Steps**
+
+1. **Select the shift**
+
+   If a name is provided, use it. Otherwise:
+   - List directories in `.nightshift/` (excluding `archive/`)
+   - Auto-select if only one exists, otherwise prompt for selection
+
+2. **Show current table state**
+
+   Read and display `table.csv` summary:
+   - Number of rows
+   - Column names
+   - Status distribution per task column (how many todo, done, failed, etc.)
+
+3. **Determine the operation**
+
+   Use the **AskUserQuestion tool** to ask:
+   > "What do you want to do?"
+
+   Options:
+   - "Add rows" — append new items to the table
+   - "Update metadata" — modify metadata column values
+   - "Reset failed items" — change `failed` statuses back to `todo`
+
+4. **Execute the operation**
+
+   **Add rows:**
+   - Ask user for the data (they can paste CSV, describe items, or point to a data source)
+   - Assign sequential row numbers continuing from the last row
+   - Set all task status columns to `todo` for new rows
+   - Append to table.csv
+
+   **Update metadata:**
+   - Ask which column and which rows to update
+   - Show a preview of the changes
+   - Confirm before applying
+   - Update the specified cells while preserving all status columns
+
+   **Reset failed items:**
+   - Ask which task column to reset (or all tasks)
+   - Show how many items will be reset
+   - Confirm before applying
+   - Change `failed` → `todo` for the specified task column(s)
+
+5. **Confirm destructive changes**
+
+   For operations that modify existing data (update metadata, reset failed):
+   - Show a summary: "This will change N cells in M rows"
+   - Use the **AskUserQuestion tool**: "Apply these changes?"
+   - Only proceed on confirmation
+
+6. **Update progress in manager.md**
+
+   After modifying the table, recalculate and update the `## Progress` section in manager.md with current counts.
+
+7. **Show result**
+
+   ```
+   ## Table Updated: <shift-name>
+
+   **Operation:** <what was done>
+   **Rows affected:** N
+   **Current state:** X total items, Y todo, Z done, W failed
+   ```
+
+**Guardrails**
+- Always confirm before modifying existing data
+- Preserve row numbering continuity when adding rows
+- Set all task columns to `todo` for new rows
+- Never reorder existing rows
+- Update manager.md progress after any change
+- Show the user what will change before applying

package/templates/opencode.jsonc

@@ -0,0 +1,92 @@
+{
+  "$schema": "https://opencode.ai/config.json",
+  "mcp": {},
+
+  // Global permissions for tools and MCP integrations
+  "permission": {
+    // File editing permissions
+    "edit": "allow",
+
+    // Bash command permissions (pattern-based)
+    "bash": {
+      "*": "ask",
+      "mkdir*": "allow",
+      "test*": "allow",
+      "cat*": "allow",
+      "head*": "allow",
+      "xargs*": "allow",
+      "curl*": "allow"
+    },
+
+    // Web fetch permissions
+    "webfetch": "allow"
+  },
+
+  // Agent configurations
+  "agent": {
+    // Nightshift manager — orchestrates shift execution
+    "nightshift-manager": {
+      "description": "Orchestrate a Nightshift shift: read manager.md and table.csv, delegate items to dev and qa agents, update status",
+      "mode": "subagent",
+      "tools": {
+        "write": true,
+        "edit": true,
+        "read": true,
+        "glob": true,
+        "grep": true,
+        "task": true
+      },
+      "permission": {
+        "bash": {
+          "*": "deny"
+        },
+        "task": {
+          "*": "deny",
+          "nightshift-dev": "allow",
+          "nightshift-qa": "allow"
+        }
+      }
+    },
+
+    // Nightshift dev — executes task steps on a single item
+    "nightshift-dev": {
+      "description": "Execute Nightshift task steps on a single table item and return structured results",
+      "mode": "subagent",
+      "tools": {
+        "write": true,
+        "edit": true,
+        "read": true,
+        "glob": true,
+        "grep": true,
+        "task": false,
+        "playwright_*": true
+      },
+      "permission": {
+        "bash": {
+          "*": "deny",
+          "mkdir*": "allow"
+        }
+      }
+    },
+
+    // Nightshift qa — verifies task completion
+    "nightshift-qa": {
+      "description": "Verify Nightshift task completion against validation criteria and report pass/fail",
+      "mode": "subagent",
+      "tools": {
+        "write": false,
+        "edit": false,
+        "read": true,
+        "glob": true,
+        "grep": true,
+        "task": false,
+        "playwright_*": true
+      },
+      "permission": {
+        "bash": {
+          "*": "deny"
+        }
+      }
+    }
+  }
+}