Managing your user stories & scenarios as "Docs in Code"

The biggest plot twist in dev tools is plain markdown files winning over fancy forms - due to agentic accessibility.

We already see this working well with:

• skills.md for agent upskilling
• claude.md for persistent context
• Spec-driven development in tools like Cursor / Antigravity

Yet, work-planning tools like Jira and Linear (built pre-AI era) are still heavily form-driven and DB-centric, which makes them not fit for agentic workflows.

Idea:

User stories and test scenarios maintained as .md files (strongly typed via frontmatter), organized into folders — with human-friendly workflows (status updates, due dates, assignees) layered on top.

What this enables:

• Plans can by synced to the repo, so coding / testing agents can read and work on them directly
• Stories and scenarios can be organized into nested folder structures (by area, journey, subsystem, team - whatever fits) - so you can get coverage insights at any granularity
• Folder structure gives agents broader context, which helps avoid "tunnel vision" of coding agents (cos they can read related stories in the folder, scenarios to cover for the story etc.)

Curious what others think:

• Would this be a better fit for your agent-heavy workflows?
• Any obvious downsides I’m missing?
• Has anyone tried something similar?

If there’s interest, happy to share what I’ve built. Here's a quick snap of what it looks like today (a pre-v1):

TestChimp - User Stories as Markdowns