Spec-kit and Github Issues/Projects

[jsgoecke]

I am all in on spec-kit and what it does. I had done some similar work on the developer side with RooCode and extending RooCommander, but adding this on the project side makes it even better.

My biggest question is how do you track the progress at the epic and user story levels with spec-kit? It seems you have to go though markdown files on a regular basis, rather than being able to use Github Issues and Projects to track as you normally would. Are there script that could run to populate issues, and then a commit hook to update them?

Trying to figure out how to use the power of spec-kit, while maintaining organization transparency and clarity of where the development process is.

[airtonix]

I'd caution against locking yourself into github.

If you just want a kanban board view, then perhaps you'd be better served by https://github.com/MrLesk/Backlog.md

This is another reason why I really want spec kit to just create tasks as separate files.

I feel like speckits value isn't in task management, it's in project discovery phase and as such it should:

• get rid of its behaviour to create branches
• store tasks as separate files instead of a checklist inside a single file.

[foertel]

I'd caution against locking yourself into github.

Me too. But it's sooo tempting.

And a strong "yes, please" to the rest of it. 👌 Please write specs, but don't try to organize my workflow ...

[gimmebytes]

I would argue, that at least SpecKit should optionally provide a way to sync tasks with Github Issues. Why? With this, you could even work, when you call it a day, and assign Copilot to those issues, working on features, while you're busy with other stuff.

@airtonix thanks, for pointing towards https://github.com/MrLesk/Backlog.md - which at least makes it easier for now, to track the progress of tasks. But ultimately, when you want to scale SpecKit in big enterprises, there is no way around of connecting the tasks with any of the major ticketing systems (also looking at you, JIRA).

[roperi]

From the point of view of Github they should aim to integrate speckit with all other tools from the github ecosystem. So I, for one, I'd like to see it integrated with Projects, for instance (and subissues for good measure).

[JeredBlu]

@localden Do it

[jsgoecke]

Seems it has been done for Issues on Github:

https://github.com/github/spec-kit/blob/main/templates/commands/taskstoissues.md

[xinity]

@jsgoecke it would be nice to have a implementfromissues then WDYT ? :)

[airtonix]

@airtonix thanks, for pointing towards https://github.com/MrLesk/Backlog.md - which at least makes it easier for now, to track the progress of tasks. But ultimately, when you want to scale SpecKit in big enterprises, there is no way around of connecting the tasks with any of the major ticketing systems (also looking at you, JIRA).

Honestly, you should just ditch speckit, it's over engineered and bloated and results in each and every chat session filling up your context window pushing you into the dumb zone.

You can architect a series of prompts that use the atlassian mcp instead. Ideally you should use a tool that lets you disable all mcp servers on your default agent/tone/mode and only enable it on your dedicated jira/planning agent/tone/mode (opencode allows you to do this).

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.