Hey there! 👋
I just recorded something that might interest you - a completely unscripted screen recording of my actual development workflow using imdone-cli with Jira and VS Code.
What's in the Video
13-minute real workflow recording
No tutorials, no demos - just me working on the imdone.io homepage while managing Jira issues as markdown files directly in VS Code. You'll see:
- How I navigate between Jira issues and code without browser switching
- Using GitHub Copilot with issue context for better AI suggestions
- CSS iterations and homepage updates in real-time
- Syncing changes back to Jira when done
- Why I keep old release notes as comments for team reference
The Bigger Picture
I've been experimenting with what I call "context-driven development" - keeping the "why" behind code changes right next to the "how" in your repository.
The video shows this in practice, but I also wrote about the broader experiment and where I'm heading next:
Recording My Experiments in Spec-Driven Development
Why Share This?
Context switching between tools kills development momentum. Every time you jump between browser tabs, scattered notes, and different interfaces, you lose mental flow.
This workflow eliminates most of that friction by keeping Jira issues as markdown files in your repo, making them first-class citizens alongside your code.
That's it! If you work with Jira and spend time in VS Code, you might find this approach useful. Let me know what you think.
Jesse
Founder, imdone.io
P.S. This is part of a larger experiment in spec-driven development that I'll be documenting as I go.
0 comments