RFC 001: Workflow config
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
RFC 001: Workflow Configuration
Status: Open for feedback
Summary
Should braid allow configuring workflow preference (direct merge vs PR)?
Options
- A: No config (current) — agents ask or use judgment
- B: Project-level —
workflow = "pr"in config.toml - C: Issue-level —
workflow: directin frontmatter
Current Lean
No configuration for now — not enough real-world experience, AGENTS.md works, can add later if needed.
Feedback Requested
- Do you configure this today?
- Have agents guessed wrong?
- Would config help?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read RFC 001 and the current AGENTS.md guidance first; the issue does not identify an implementation file or test entry point. Resolve whether workflow configuration is needed and which scope, if any, should be supported before defining implementation work and acceptance tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100