Replies: 1 comment
-
|
By the way. I can easily make a custom skill or instruction in AGENTS.md to implement this downgraded workflow. I would like to have the graphql api though. Here's what I'm using currently: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I very much like beans simple concept of storing tasks in markdown. The TUI is
great and the whole cli experience is nice. What I'm missing is workflow
flexibility. My first use case is not the autonomous beans/agent worklow.
I want rather want to have a prompt buffer for my OpenSpec workflow. The task
description of a bean should be the input for an /opsx:explore or
/opsx:propose. In this simple workflow I don't want beans to take over the
/change-.../tasks.md. I just want to store my steering epic and after
/opsx:apply I could be closed.
What features I would like to see for this workflow:
I saw several PR/issues which could lead to this flexibility but I'm uncertain
if the author of beans is sharing the vision of this flexibility.
@hmans Is this use case something you want to support with later versions?
Beta Was this translation helpful? Give feedback.
All reactions