Add Long-Running Agent Harness commands and portfolio README

Publish 14 Claude Code slash commands (session lifecycle, multi-agent coordination, utilities) and 1 Cursor rule to showcase multi-session project management and agent workflow automation skills.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Made-with: Cursor

Author: DougState

.claude/commands/add-agent.md

@@ -0,0 +1,69 @@
+---
+description: Add a new agent role to a multi-agent project
+argument-hint: <agent-name>
+---
+
+Add a new agent role to an existing multi-agent project.
+
+Arguments: $ARGUMENTS
+
+## Prerequisites
+
+- feature_list.json must exist
+- Project should already be in multi-agent mode (if not, suggest `/enable-multi-agent` instead)
+
+## Steps:
+
+1. **Read current feature_list.json**
+
+   If file doesn't exist, error: "No feature_list.json found. Run `/init-harness` first."
+
+   If `multi_agent_mode` is not true, error: "Project is not in multi-agent mode. Run `/enable-multi-agent agent1,agent2,...` first."
+
+2. **Parse agent name from arguments**
+
+   Trim whitespace, lowercase.
+
+   If no agent provided, error: "Please specify an agent name. Example: `/add-agent testing`"
+
+3. **Check for duplicates**
+
+   If agent already exists in the `agents` array, error: "Agent '[name]' already exists."
+
+4. **Add agent to array**
+
+   Append the new agent to the `agents` array.
+
+5. **Update feature_list.json**
+
+   - Add agent to `agents` array
+   - Update `last_updated` to today's date
+
+6. **Display confirmation**
+
+   ```
+   Agent added: [name]
+
+   Current agents: design, architect, api, [name]
+
+   To assign features to this agent:
+     /add-feature [name]:category "Feature name" Description
+     /reassign-feature FEAT-001 [name]
+   ```
+
+## Example usage:
+
+```
+/add-agent testing
+```
+
+Output:
+```
+Agent added: testing
+
+Current agents: design, architect, api, testing
+
+To assign features to this agent:
+  /add-feature testing:test "Integration tests" Add integration test suite
+  /reassign-feature API-003 testing
+```

.claude/commands/add-feature.md

@@ -0,0 +1,66 @@
+---
+description: Add a new feature to feature_list.json for tracking
+argument-hint: [agent:]<category> <name> <description>
+---
+
+Add a new feature to the feature_list.json tracking file.
+
+Arguments: $ARGUMENTS
+
+Parse the arguments to extract:
+- agent (optional): If first word contains a colon, split it as `agent:category`
+- category: First word (e.g., "core", "security", "ui", "api", "test"), or after the colon if agent prefix used
+- name: Second word or phrase in quotes
+- description: Remaining text
+
+## Steps:
+
+1. Read the current feature_list.json
+
+2. Check for multi-agent mode:
+   - If `multi_agent_mode: true` and no agent prefix was provided, check if there's a `.current-agent` file
+   - If neither exists, warn: "This project uses multi-agent mode. Use `/add-feature agent:category ...` or run `/session-start` first to set your agent role."
+
+3. Determine the next feature ID:
+   - Look at existing features in the same category
+   - Generate ID like CATEGORY-NNN (e.g., CORE-003, SEC-001)
+   - Use uppercase category prefix
+
+4. If the category doesn't exist in "categories", add it with:
+   - priority: "medium" (can be adjusted)
+   - description: Infer from category name
+
+5. Add the new feature with:
+   - id: Generated ID
+   - category: Provided category
+   - assigned_to: Agent name if provided or from `.current-agent`, otherwise `null`
+   - blocked_by: [] (empty array)
+   - name: Provided name
+   - description: Provided description
+   - status: "failing" (new features start as failing)
+   - file: "" (to be filled when implementing)
+   - test_criteria: "" (to be filled when implementing)
+
+6. Update the summary:
+   - Increment total
+   - Increment failing
+   - Update last_updated to today
+
+7. Show the added feature and updated summary
+
+## Example usage:
+
+### Single-agent mode (or unassigned):
+```
+/add-feature security "Input validation" Validate all user inputs to prevent injection attacks
+/add-feature ui "Dark mode toggle" Add toggle switch to enable dark mode theme
+```
+
+### Multi-agent mode (with agent assignment):
+```
+/add-feature api:security "Rate limiting" Implement rate limits for API endpoints
+/add-feature design:ui "Dashboard layout" Create responsive dashboard grid
+/add-feature architect:core "Database schema" Design and implement database models
+```
+
+The part before the colon is the agent role, the part after is the category.

.claude/commands/commit-push.md

@@ -0,0 +1,24 @@
+Commit all changes to git and push to the remote repository. Follow these steps:
+
+1. Run `git status` to see all untracked and modified files
+2. Run `git diff` to see both staged and unstaged changes
+3. Run `git log -5 --oneline` to see recent commit messages for style reference
+4. Analyze the changes and draft a commit message that:
+   - Summarizes the nature of the changes (new feature, enhancement, bug fix, refactoring, etc.)
+   - Focuses on the "why" rather than the "what"
+   - Is concise (1-2 sentences)
+   - Follows the style of recent commits in this repository
+5. Add all relevant files to staging with `git add .` (exclude files that shouldn't be committed like .env, credentials.json, etc.)
+6. Create the commit with the message ending with:
+
+   🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+   Co-Authored-By: Claude <noreply@anthropic.com>
+
+7. Push the changes to the remote repository with `git push`
+8. Run `git status` after the push to verify success
+
+IMPORTANT:
+- Do not create a commit if there are no changes
+- Warn the user if attempting to commit files that likely contain secrets
+- Use a HEREDOC to pass the commit message for proper formatting

.claude/commands/enable-multi-agent.md

@@ -0,0 +1,105 @@
+---
+description: Enable multi-agent mode for an existing project
+argument-hint: <agent1,agent2,...>
+---
+
+Enable multi-agent mode for an existing project by adding agent roles to feature_list.json.
+
+Arguments: $ARGUMENTS
+
+Parse the comma-separated list of agent roles (e.g., `design,architect,api`).
+
+## Prerequisites
+
+- feature_list.json must exist (run `/init-harness` first if not)
+- Project should not already be in multi-agent mode
+
+## Steps:
+
+1. **Read current feature_list.json**
+
+   If file doesn't exist, error: "No feature_list.json found. Run `/init-harness` first."
+
+   If `multi_agent_mode` is already true, warn: "Project is already in multi-agent mode with agents: [list]. Use `/add-agent` to add more agents or manually edit feature_list.json."
+
+2. **Parse agent roles from arguments**
+
+   Split by comma, trim whitespace, lowercase all roles.
+
+   If no agents provided, error: "Please specify agent roles. Example: `/enable-multi-agent design,architect,api`"
+
+3. **Update feature_list.json**
+
+   Add to the root object:
+   ```json
+   {
+     "multi_agent_mode": true,
+     "agents": ["agent1", "agent2", "agent3"]
+   }
+   ```
+
+4. **Handle existing features**
+
+   If features already exist, ask the user:
+
+   "You have [N] existing features. Would you like to assign them to agents now?"
+
+   Options:
+   - **Yes, assign now** - For each feature, prompt which agent (or "unassigned")
+   - **No, leave unassigned** - Set all existing features' `assigned_to` to `null`
+   - **Assign by category** - Auto-assign based on category-to-agent mapping (prompt for mapping)
+
+5. **Ensure feature schema compatibility**
+
+   For each existing feature, add if missing:
+   - `assigned_to`: null (or assigned agent)
+   - `blocked_by`: []
+
+6. **Update summary**
+
+   - Update `last_updated` to today's date
+
+7. **Display confirmation**
+
+   ```
+   Multi-agent mode enabled!
+
+   Agents: design, architect, api
+
+   Features:
+     Assigned: X
+     Unassigned: Y
+
+   Next steps:
+     - Use `/add-feature agent:category "name" description` to add agent-assigned features
+     - Run `/session-start` to select your agent role
+     - Use `/reassign-feature FEAT-001 agent` to reassign features
+   ```
+
+## Example usage:
+
+```
+/enable-multi-agent design,architect,api
+```
+
+Output:
+```
+Multi-agent mode enabled!
+
+Agents: design, architect, api
+
+You have 5 existing features. Would you like to assign them to agents?
+> Assign by category
+
+Category mapping:
+  ui → design
+  core → architect
+  api → api
+  security → api
+
+Features assigned:
+  UI-001 → design
+  CORE-001 → architect
+  API-001, API-002 → api
+  SEC-001 → api
+```

.claude/commands/history.md

@@ -0,0 +1,29 @@
+---
+description: Browse and display files from the session history folder
+argument-hint: [filename]
+---
+
+Read and display a file from the `docs/history/` directory.
+
+File to view: $ARGUMENTS
+
+## Steps
+
+1. Locate the file at `docs/history/$ARGUMENTS`
+2. Display the content (renders images visually, shows markdown/text inline)
+
+## Examples
+
+```bash
+/history SESSION-2025-08-01-monthly-insights.md
+/history project-architecture-flowchart.svg
+/history napkin-insights-mockup.png
+```
+
+## Notes
+
+- Works with any file type (markdown, images, text files, SVGs, etc.)
+- Images are displayed visually in the interface
+- Markdown and text files show their content
+- Use this to review past session notes, decisions, and project documentation
+- File path is relative to the `docs/history/` directory