Proposal: Consider Using JSON Format for SpecKit Generated Files #1032
Replies: 3 comments 2 replies
-
|
Please dont, json is ideal for machines, but terrible for humans. Yaml if you must... |
Beta Was this translation helpful? Give feedback.
-
|
I’ve been converting my tasks.md files into .json and the results have been fantastic. I’m using Sonnet 4.5 to create the structured task plan, then I run two additional chat windows with Haiku, each working through their assigned tasks. If one agent depends on another, that dependency is marked in the .json, and the agent will pause automatically until the other has finished. You can even have them poll for approval or unblock status. Using this setup, I implemented an entirely new canvas feature overnight — and only had one minor bug. Overall, extremely successful. |
Beta Was this translation helpful? Give feedback.
-
|
The spec needs to be easily readable by both humans and the AI. I think markdown is perfect for that. I can't imaging reading specs all day in JSON or what if you have to ask a business analyst for an opinion on the spec. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to suggest a possible improvement for SpecKit regarding the current format of the files generated (.md/Markdown). I think it could be worth considering using JSON files instead, as this would bring several key advantages:
For these reasons, I believe it would be highly valuable to consider JSON as the format for SpecKit's main artifacts (plan, tasks, constitution), enabling greater potential for MCP tooling and automation.
Beta Was this translation helpful? Give feedback.
All reactions