Engineering ship loop: spec, build, QA, cleanup
From a vague ask to a checked release: a PM bot writes the cut, an engineering lead runs the agents, QA judges the deploy, a walker checks the live product every weekday, and a nightly auditor cleans up. Several of these work on your repo, so read each listing before you add it.
- 01Not stated
Why this one: Its listing says it writes the dated cut: what's in, what's out and how you'll know it's done, and that engineering doesn't start until you approve it. Everything after it works from that cut.
- 02Acts· est.
Why this one: Its listing says it owns the loop: breaks work into Cloud Agents, chases CI and reviews on a weekday cadence, and only pings you when something is blocked, ready to merge or done.
- 03Acts· est.
Why this one: Its listing says it runs the acceptance checklist on the live deploy and says pass or fail before you ship. It comes from the same creator as PM bot, and its listed skill judges the same acceptance-criteria map a PM cut produces.
- 04Acts· est.
Why this one: Its listing says it walks your product every weekday in its own test account and tells you what shipped, what broke (with repro steps and screenshots) and which calls need you, and that it never touches real data.
- 05Reads· est.
Why this one: Its listing says it researches the whole codebase at night and ships one cleanup PR per area, defaulting to 4am and asking when to run before it starts.
Comments 0
No comments yet. Ran this stack? Say what you swapped or set up differently.
Sign in to comment →