Show HN: Product as Code – YAML-based product management for AI coding workflows
Show HN (score: 6)Description
This is when I started experimenting with creating work plans. Initially simple todo list, but it felt like "product vibing", so a bit more sophisticated later on. I started seeing value in it.
The one day it hit me. Why not use the same GitOps principles to managing product tickets? I started playing with that and really liked the way it worked.
After a chat with a friend of mine, I realised that a standard or a spec would be something really useful. You could then create all sort of tooling around this.
I took an inspiration from the way kubernetes yaml are used, cause I find it quite neat.
You can view examples here: https://spec.productascode.org/draft/#sec-Epic-Example-YAML-
Key design decisions so far:
1. YAML over JSON: Human-readable, git-diff friendly, excellent tooling ecosystem 2. Hierarchical structure: Epics → Tickets → Tasks (matches development workflow) 3. Atomic tickets: Each ticket = one branch = one PR (prevents scope creep) 4. ISO 8601 timestamps/durations: Machine-parseable time data
If I manage to create an epic with a bunch of tickets in backlog, then my favourite part of work is to tell Claude Code: "Close the current ticket, and start another one".
Here is the link to the post which has links to draft spec and GitHub repository.
Currently working on v0.1.0 and I would love to hear your thoughts.
More from Show
Show HN: Visual Database Schema Designer (Angular 21 and .NET 10)
Show HN: Visual Database Schema Designer (Angular 21 and .NET 10) Hi HN, OP here.<p>I built this because I was frustrated with the current state of DB design tools. They are usually either heavy enterprise desktop apps (like DataGrip/Workbench) or simple drawing tools that don't export usable code.<p>I wanted a "VS Code-like" experience in the browser: dark mode, strict typing, and instant visual feedback.<p>The tech stack is quite aggressive: - Frontend: Angular 21 (Latest). I'm using Signals exclusively for the graph state management to handle 100+ nodes without layout thrashing. - Backend: .NET 10 for DDL generation and schema validation.<p>Current features: - Visual Table/Column editor. - Drag & drop relationships (1:N handling). - Exports to PostgreSQL DDL and Entity Framework Core.<p>It's an MVP, so I'm looking for feedback on the graph interaction and the UI feel.<p>Does the "IDE-like" layout work for you for this kind of task?
Show HN: Opal Editor, free Obsidian alternative for markdown and site publishing
Show HN: Opal Editor, free Obsidian alternative for markdown and site publishing A fully featured markdown editor and publisher. Free, open-source and browser-first (no backend required). Built with modern technologies like React, TypeScript, Shadcn/UI, and Vite. (thoughtfully crafted, not vibe coded)
Show HN: Control Claude permissions using a cloud-based decision table UI
Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy/gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf / when --force; allow cleanup only in node_modules; ask on network calls like curl/wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why
Show HN: Claude Code Scheduler
Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.
No other tools from this source yet.