Ver 2.0 Roadmap

[jellydn]

Hi @CasJam,

Thank you for the great work. I wonder if you could share the roadmap for version 2. The reason is that other people are putting the PR, but it's closed due to the new version. For example, Agent OS for GitHub Copilot.

I'd like to share some thoughts and ideas after trying your tool:

• How to update/upgrade agent-os for the existing project? Possibly a self-update command.
• How to add a custom flow for ad hoc tasks or chore/mics tasks that aren't covered by the current product.
• Are there any plans to support other editors like Zed?

[ChenReuven]

@CasJam is there any update about support for Github Copilot?

[mikelittle]

How to add a custom flow for ad hoc tasks or chore/mics tasks that aren't covered by the current product.

I added a /fix command to handle my natural tendency to ask for bug fixes or tweaks straight after testing a new feature. Just two files:

1. .agent-os/commands/fix.md

# Fix

Handle ad-hoc code changes, bug fixes, and small optimizations with proper git workflow.

Refer to the instructions located in this file:
@.agent-os/instructions/execute-fix.md

and 2. .agent-os/instructions/meta/execute-fix.md

# Execute Fix Workflow

## Purpose

Handle ad-hoc code changes that don't go through the formal create-spec/execute-tasks process but still require proper git workflow and code review. This includes bug fixes, small optimizations, documentation updates, and code improvements.

## Mandatory Prerequisites

1. **ALWAYS read best-practices.md first** to load git workflow requirements
2. **NO EXCEPTIONS**: All code changes must go through branch/PR process
3. **Branch naming**: Use format `YYYY-MM-DD-brief-description`

## Workflow Steps

### 1. Initial Setup and Analysis
- Read `.agent-os/standards/best-practices.md` to load git workflow requirements
- **If no specific fix details provided**, prompt user for:
  - **What needs to be fixed?** (describe the issue, bug, or improvement)
  - **Where is the problem?** (file names, functions, or general area)
  - **Expected behavior** vs current behavior (if applicable)
  - **Any error messages** or symptoms observed
  - **Priority level** (urgent fix, optimization, nice-to-have)
- Understand the fix/change requested
- Identify affected files and scope of change
- Create todo list for tracking progress

### 2. Create Feature Branch
\```bash
git checkout -b YYYY-MM-DD-brief-description
\```
Where:
- `YYYY-MM-DD` is today's date
- `brief-description` is a short kebab-case description of the fix

### 3. Implement Changes
- Make the requested code changes
- Follow coding standards from best-practices.md
- Keep changes focused and minimal
- Test changes if tests are available

### 4. Commit Changes
- Stage only relevant files
- Write descriptive commit message explaining:
  - What was changed
  - Why it was changed
  - Impact of the change
- Include standard footer:
  \```
  🤖 Generated with [Claude Code](https://claude.ai/code)

  Co-Authored-By: Claude <[email protected]>
  \```

### 5. Create Pull Request
- Push branch to remote
- Create PR with descriptive title and body
- Include:
  - Summary of changes
  - Reason for fix
  - Testing performed (if any)
- Return PR URL to user for review

## Command Usage Examples

### With Specific Details
- "Fix the bug in the authentication system where users can't login"
- "Update the error message in config.php to be more user-friendly"
- "Optimize the database query performance in UserController::getUsers()"
- "Add missing validation to user input in the registration form"
- "Fix typos in the documentation README.md"

### With Minimal Information (requires prompting)
- "/fix" (no parameters - prompt for all details)
- "/fix authentication bug" (prompt for location, symptoms, expected behavior)
- "/fix slow queries" (prompt for specific files, measurements, priority)
- "/fix typos" (prompt for which files, specific sections)

### Information Gathering Template
When details are missing, use this template to gather information:

\```
I need more details to help you with this fix:

1. **What specifically needs to be fixed?**
   - Describe the issue, bug, or improvement needed

2. **Where is the problem located?**
   - File names, functions, classes, or general areas
   - If unknown, describe where you've observed the issue

3. **What's the current vs expected behavior?**
   - What happens now vs what should happen
   - Any error messages or symptoms

4. **How urgent is this fix?**
   - [ ] Critical (blocking functionality)
   - [ ] Important (affects user experience)
   - [ ] Optimization (performance improvement)
   - [ ] Nice-to-have (minor improvement)

Please provide as much detail as possible so I can create an effective solution.
\```

## Error Handling

If any step fails:
- Report the specific error
- Suggest resolution steps
- Do not proceed to next step until current issue is resolved
- Maintain branch state for user to review

## Success Criteria

- ✅ Feature branch created with proper naming
- ✅ Changes implemented and tested
- ✅ Commit message follows standards
- ✅ PR created successfully
- ✅ PR URL provided to user
- ✅ No direct commits to main branch

Note: I had to escape the embedded triple back tics to paste here.

[CasJam]

I just posted a progress update today: #159