Hacker News new | ask | show | jobs
by zameermfm 41 days ago
With AI IDEs, Personally I had to generate a tons of md files for planning a task, analysis on the code for something or other, a task doc for a feature - a summary to paste into the clickup ... and I saw many devs keeps on generating them, and all tucked away into folders. Good, okay.

For the company I'm currently working I had made a VSCode extension where I can sync the task doc with clickup via frontmatter.

I decided to take it to next level as a side project. I built a CI integrated, git-native, agent template transformable syncing pipeline with git MD files to any project management tools. That means, either you can save your md files vanilla in your wiki (thus using the clickup AI search to dig up later, get insights etc) or you can use a AI agent template transformer to turn it into a task template (Background, acceptance criteria, functional requirements etc.) and update or create a task on a board.

I've been working on it now. I don't know how it will fare, but I feel like product is coming up nice.

https://mdspec.dev

1 comments

Great idea!

I was actually working on last weekend with something that has similarities. I am working on USM.tools, which allows specifying your services in structured way.

There is a need to specify some of the data in semi-structured way, and I am using markdown for that.

So there is this interesting relationship between unstructured, semi-structured and structured data, and markdown hits that middle ground.

Can I suggest you make some Jira etc. templates on your landing page clickable, so a visitor can grasp your idea more easily? For me it was not clear whether the specs are just plain markdown, or do you have some additional tagging there.

Great idea you got, what would be a classic use case? We have a data source and we can define the API structure to get them?

Sure! thanks! thats good idea, to have it clickable and true that needs needs to be easily understandable.

Service management is business oriented, what is the service we are providing and how do we deliver it, and how do we agree with the customer what we deliver. And when the data is structured, other interesting oppurtinities become possible.

This particular use case is people working together to collect data in a workshop. 10 people don’t want to see somebody searching for the right place in a form, it interrupts the flow of the meeting. You need to capture the ideas raw, and then structure later. That is where question anout how unstructured data is captured in strucured format pops up.

It is a workflow I directly support in my tool, not a generic tool like yours.