Skip to content
Nichr
Developer toolsNew techTop 10% of today's analysed ideas

In-repo ticket files for AI coding agents

Build a lightweight tasks-as-code tool: tickets stored as markdown or YAML files inside the repo, synced with git branches and commits, and exposed via a simple API or MCP server so AI coding agents (Claude Code, Cursor, etc.) can read and update tasks without leaving the codebase. Target solo developers and small teams running AI agents who want to avoid context-switching to Jira or Linear.

via Hacker News
Original post

What to build

A CLI + lightweight MCP server that stores tickets as markdown/YAML files inside a git repo, auto-links them to branches and commits, and exposes a simple read/write API so AI coding agents (Claude Code, Cursor) can pull their next task and update status without leaving the terminal.

Solo developers running AI coding agents are duct-taping task tracking out of markdown files and TODO comments because Jira/Linear force a context switch away from the repo and the agent's workflow.

Demand

Solo builders and small teams running AI coding agents want their task backlog inside the same context window as their code, so the agent can read and update tasks without a human relaying tickets back and forth.

  • Hacker NewsEngagement

    "Tasks as Code: Move Your Tickets into the Repository" — 46 points, 50 comments on HN, indicating high engagement with the core idea at the source.

  • Opportunity descriptionAnalysis

    Target users identified as solo developers and small teams running AI agents who want to avoid context-switching to Jira or Linear.

Stack

  • Markdown/YAML frontmatter for ticket schema
  • Git CLI (libgit2 or simple-git bindings) for branch/commit linking
  • MCP server SDK for agent tool exposure
  • SQLite or just filesystem for local indexing/search
  • Node.js or Go for the CLI binary
  • GitHub Actions for commit-to-ticket status sync

Solo + AI difficulty

The core loop — parsing markdown tickets, watching git for branch/commit references, and wiring an MCP server — is a buildable weekend-to-2-week MVP for one person with AI help; the hard part is designing a ticket schema and conflict-resolution model that survives merges and multi-branch work without turning into a git-merge nightmare. A CLI-only, single-user v1 (no real-time sync, no web UI) is the realistic scope to ship fast.

Entry threshold
Very low barrier, a CLI tool or small MCP server can be built solo in days; the main competition is a handful of existing open source projects (git-bug, backlog.md style tools) and the pull of entrenched tools like GitHub Issues and Linear.
Window
6-12 months

Where to find first users

  • Hacker News (post a Show HN, the original signal already drew 46 points/50 comments on an adjacent post)
  • r/ClaudeAI and r/cursor (communities actively discussing AI coding agent workflows)
  • Product Hunt launch
  • Indie hacker / build-in-public communities (Indie Hackers, X/Twitter #buildinpublic)

Competitors

Counter-signals & risks

  • Existing project management tools (Jira, Linear, GitHub Issues) already have mature ecosystems, integrations, and MCP connectors, reducing the need for a new standalone tasks-as-code tool.

  • Storing tasks as files in git introduces merge conflicts, lacks multi-user real-time collaboration features, and may not scale to larger teams or non-technical stakeholders.

  • No historical match and a middling score (0.52) suggest this is an early, unvalidated niche idea without demonstrated market demand or traction signals.

Original title: Tasks as Code: Move Your Tickets into the Repository

Related signals

  • Developer tools#3

    Paid de-AI-slop design fixer for vibe coders

    Build a paid design-polish toolkit for vibe coders: a Claude/Cursor skill pack or lightweight SaaS that scans an AI-generated app's UI and rewrites it with a real design system (typography, spacing, color, component variants) so it stops looking like generic AI output. Sell it as a one-time skill pack on Gumroad or a small subscription for continuous design audits, targeted at solo builders shipping apps made with Claude Code, v0, Bolt, or Lovable.

    Demand
    9/10
    measured
    Buildability
    9/10
    est.
    Competition
    8/10
    est.
    via GitHub
    11 competitor
  • Developer tools#6

    Per-customer LLM spend caps for micro-SaaS builders

    Build a lightweight spend-guardrail proxy for solo AI micro-SaaS builders: a drop-in layer between their app and OpenAI/Anthropic that tracks per-customer token spend, enforces hard caps or auto-throttles runaway accounts, and sends Slack or email alerts before a bug or heavy user blows past their margin. Sell it as a usage-based add-on priced per monitored account or per API call.

    Demand
    5/10
    est.
    Buildability
    7/10
    est.
    Competition
    5/10
    est.
    via Reddit
    44 competitors
  • Developer tools#3

    AI agent starter kits for the PHP developer ecosystem

    Package phpClaw into a turnkey AI-agent starter kit for the huge existing PHP/Laravel/WordPress developer base: ready-made agent templates (support bot, data-extraction agent, internal ops agent) with pre-built tool connectors, memory stores and safety guards, sold as a paid extension pack or hosted agent-hosting service for PHP shops who want to add AI agents without switching stacks to Python or Node.

    Demand
    1/10
    measured
    Buildability
    8/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
In-repo ticket files for AI coding agents — Nichr