Agentic Software Dev

A single SKILL.md file is enough for personal use, but it doesn’t scale once you want to version it, bundle it with agents and hooks, or share it with teammates. This post covers how to package skills into a plugin and distribute that plugin through a marketplace. You probably don’t need plugins for a personal project or a quick one-off customization. You do need them once you want to share with teammates, distribute to a community, cut versioned releases, or reuse the same setup across projects. ...

Many agentic workflows converge on the same shape: write a Markdown file at the root of your repo, point your agent at it, and let it loop until it meets a stated goal. Test-driven development is a natural fit for that shape — the tests are the goal, and “all tests green” is an unambiguous exit condition the agent can check without you. The basic loop In this paradigm you ask the agent to write tests first. You review them (or have another agent review them), then ask the agent to implement the feature until every test passes. You revise the tests a little, the agent revises the code a little, and when everything is green you move to the next feature — with a fully testable one behind you. ...

This post explains the AI coding workflow of Y Combinator’s CEO — how he uses GStack for ideation, building, and deployment. What is gstack gstack is a collection of SKILL.md files that give your AI agents personas for different stages of the software/product development life cycle. A normal software sprint runs through roughly these stages: 1 think → plan → design → build → review → test → ship In gstack, there is a SKILL.md file (often several) for each of these stages. You invoke them to guide your agents toward the goal (generating code, a specification, ideation, etc.). ...