12 comments

  • gbro3n 2 hours ago
    This looks great. Building right into the editor looks like a solid way to go. I built "Agent Kanban" (anextension) for VS Code to enforce a similar "plan, tasks, implement" flow as you describe. That flow is really powerful for getting solid Agentic coding results. My tool went the route of encouraging the model via augmenting AGENTS.md and having the Kanban task file be markdown that the user and agent converse in (with some support for git worktrees which helps when running multiple sessions in parallel): https://www.appsoftware.com/blog/introducing-vs-code-agent-k...
  • digitaltrees 1 hour ago
    I have settled on the same approach as you except I have the agent create a roadmap.md in an /agile folder with numbered epics containing sprints, user stories and other context.
  • kelsolaar 5 hours ago
    • VerifiedReports 1 hour ago
      Look out, you're going to get downvoted by the fact-averse.
  • simple10 3 hours ago
    Really cool. I've been building a mission control system (multi agent orchestration) that follows very similar patterns of spec driven development, steering, and task management. Having this baked into an IDE is a great idea.

    For observability, would be amazing to have session replay or at least session exploration built in. Kinda like git history but tied to tasks and tool use instead of file diffs.

  • jv22222 3 hours ago
    How does modo help vs using a skill or claud.md that says to always do this?

    Not a critique just giving you a chance to sell it :)

    • moropex 1 minute ago
      yeah this is my question too. a good CLAUDE.md with some structure goes a long way already
  • esafak 6 hours ago
    What did you learn?
  • VerifiedReports 1 hour ago
    Modo is a 3-D modeling tool. Why is this named after it?

    Yes, downvote a fact.

  • seifbenayed1992 45 minutes ago
    [dead]
  • jeremie_strand 1 hour ago
    [dead]
  • xjtumj 2 hours ago
    [flagged]
  • 0gs 6 hours ago
    [dead]
  • darshil2023 6 hours ago
    [dead]