alextes / alextes/braid

brd init suggestion

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
7
Forks
0
PR merge metrics
No merged PRs in 30d

Description

I just installed and initialized brd in one of my repos and noticed the instructions it injected into AGENTS.md was kind of long (~ 100 lines) and maybe this context doesn't need to be in every context window I open.

Might I suggest what I've noticed other agentish tools doing that seems to really be working well. I think this will obviously depend on the agent in use but taking claude as an example, does .claude/ exists and if it does mkdir .claude/skills/using-brd and write everything to a local skill @ .claude/skills/using-brd/SKILL.md. That's what I've done with the instructions locally anyway and so far so good. Maybe create a dedicated skill or plugin too that can be installed globally. if you autodetect that then nothing to be done :)

Great work, btw. I found this project when following a link you shared on an issue in the beads repo. I had a similar idea too, storing things in markdown, but you've actually gone and made the thing, which is fantastic imo. Great tui even.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the brd init command and how it writes AGENTS.md. Review the proposed .claude/skills/using-brd/SKILL.md location and decide how agent-specific installation should be handled. Done means initialization avoids unnecessary context in AGENTS.md while preserving the brd instructions through the agreed skill or plugin path.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.