What it does
Lightweight automation for recurring dev operations. Scripted workflows that occupy the middle ground between shell aliases and full CI/CD pipelines — for operations too complex to alias but too lightweight to pipeline.
Architecture / Key capabilities
- Middle-ground automation — Targets the gap between one-liner shell aliases and heavyweight CI/CD configurations, where most recurring dev tasks actually live
- Scripted workflow composition — Chain multiple CLI operations into repeatable, named workflows that can be triggered with a single command
- Multi-project operator focus — Designed for developers managing many concurrent projects who repeat similar operational patterns across repos
- Minimal configuration overhead — Workflows are defined with minimal boilerplate so adding a new automation is fast, not a project in itself
- Shell-native integration — Runs in the operator’s existing shell environment without requiring a daemon, server, or separate runtime
Key numbers
MISSING — workflow count, operation coverage
Current phase
Phase 1 visualizer implemented and functionally validated. Amp thread dataset workstream beyond extraction viability. Coverage audit written (2026-03-29). Main remaining gaps: manual app-level QA + minimum lifecycle controls.
Status
Active — P1: run Phase 1 manual QA checklist, add minimum menu lifecycle controls. P2: controlled amp --execute validation, job estimate validation.
Links
MISSING — Repository URL