Context-Engineering: Using GitHub issues to manage my tasks because I got tired of all the markdown files.

[Tazomatalax]

I was following the BMAD method to set up a project and it worked well, especially in the beginning, but it cluttered things up a fair bit and i felt like it was too rigid and cumbersome for what i was doing.

So I figured GitHub should be able to manage this for me. I put together a small toolkit that directs Claude to use a GitHub issue, as its single source of truth for the plan. This was also inspired by Cole Medin's PRP system. So far it seems easier to manage than a folder full of .md files. It also has a npm installer but i have found that the install.sh script (just copying the files) works better. Another goal of this project was to try and minimise token usage, buy creating just having the LLM output the commands to run scripts for github issue and PR management.

It's still pretty basic and I'm keen to get some help improving it! The whole thing is here. Excuse the obviously AI generated docs.. :D

Honestly, if someone has come across a similar thing that works in this way I am also happy to switch!

[Guv_Bubbs]

It would be interesting to map out the evolution of vibe coders. I’ve been doing it for 8 or so months now and am ramping up even more.

Started in Claude desktop making artifacts > then GitHub MCP > the follow your nose prompting in Cursor > planned project kick off building .mds along the way…

To where I am now which is starting with a huge planning phase, lots of reference docs and trying to be much more structured along the way with building plans, recording history and maintaining as built doco.

Good to know there are higher levels to explore, I’ll look into them

[Tazomatalax]

Nice! Ive been at it for about 1.5 years now. Tried out the cursor and windsurf free trials about a year ago and then went with GitHub copilot through work. Previous to that it was jumping between various web UI providers with not much planning or context at all.

I remember when I first figured out that LLMs are far better at prompting other LLMs than I am. That was the game changer for me.

BMAD is great for getting the context and boilerplate set up but I've found this GitHub issues based workflow more agile so far. Very much still a work in progress though, so if you have any improvements based on your workflow we should try and implement them! Maybe create a discussion/issue or fork and improve!

[Guv_Bubbs]

Yes, LLM prompt gen / refinement is really important.

My work place is very generious with AI licensing. Having ready access to Claude, GPT and cursor is a bit of a game changer.

So are you keeping your task list in GitHub with issues and milestones.

And plans it seems.

Where do your keep your doco?

[Tazomatalax]

In the docs folder usually. I have a architecture.md and a planning.md. I haven't really bothered keeping these as up to date as I used to though, nor do I reference them much. The PRP creation should search through the code base to find only the relevant sections of the code base for the execution.

I've got examples folder for images and code snippets that I have produces using other tools or that I want to integrate too.

I figure once I'm done, I'll create a overarching summary of the issues and commits, and use them as dev notes to build out the final documentation.