founder-os: Command for Claude Code

Request Plan Revision

Request changes to a research plan that's in needs_review status. This creates a revision loop where the agent updates the plan based on feedback.

Arguments

• $ARGUMENTS - (Optional) Task ID of the plan to revise. If not provided, show all plans awaiting review.

Process

1. Read .claude/queue/backlog.json to find items with status: "needs_review"

2. If no task ID provided:

   • List all items with needs_review status
   • Ask which plan to revise

3. If task ID provided (or after selection):

   • Read the plan file at the item's plan_file path
   • Display the plan for context

4. Gather revision feedback:

   Ask the user: "What changes do you want to the plan?"

   Collect specific feedback. Good revision requests:

   • "Consider approach X instead of Y"
   • "The risk section doesn't address Z"
   • "Split this into two phases"
   • "Add more detail to the implementation steps"
   • "What about impact on {system}?"

5. Update the research task:

   {
     "status": "pending",
     "revision_requested": true,
     "revision_count": {previous count + 1},
     "revision_feedback": "Specific feedback from founder",
     "updated": "ISO timestamp"
   }
   

   Keep all other fields unchanged. The task stays in backlog with pending status so /queue:work will pick it up again.

6. Report:

   • Revision requested for {task ID}
   • Feedback recorded
   • "The agent will pick this up on next /queue:work and update the plan"

Revision Workflow

Plan created → needs_review → /queue:revise → pending (with feedback) → agent revises → needs_review → repeat or /queue:approve

How the Agent Handles Revisions

When /queue:work picks up a task with revision_requested: true:

1. The agent reads the existing plan file
2. Reads the revision_feedback
3. Updates the plan to address the feedback
4. Sets status back to needs_review
5. Clears revision_requested

This creates a natural review loop until the founder approves.