Evergreen engineering standards I hold code to — the judgment layer that AI-slop resistance needs on top of the mechanical quality stack. Project-structure conventions, worktree isolation (every line of work in its own tree; bare primaries need a sibling), GitHub API discipline, exit-code integrity (never read a…
Feature lifecycle management with state, search, epic dispatch, and review gates. Capture ideas (idea.md), plan (plan.md), and ship (shipped.md) with file-presence lifecycle plus orthogonal state (active/paused/replaced/abandoned). Single-feature autopilot and parallel-wave epic dispatch — every subagent in its own…
One-shot setup for a new repo's standards: feat → dev → main promotion model with a PR CI gate, GitHub repo setup (branch protection, deploy environments, required reviewers, environment-scoped OIDC), and the language-agnostic quality stack (lefthook hooks + a shared justfile, run identically in CI). The /project-init.
Code-quality workflow: surface, triage, and resolve static-analysis findings (skylos for Python, fallow for TS/JS) with the same backlog-and-epic discipline that feature-workflow provides for feature work. Read-only quality-audit, structured quality-unblock that refuses bare suppressions, hook self-verification that…
Sprint planning and team coordination. Triage backlogs by deadline, assign work with self-service specs, audit feature specs for completeness, and generate team communication. Designed for small teams (2-6 devs) with mixed experience levels preparing for demos or releases.
Guided workflow to deploy Node.js/Express apps to AWS serverless architecture. Analyzes your app, scaffolds infrastructure, and deploys with CDK — all with step-by-step explanations for beginners.
★not rated 14 16d agoA
tokens not measured
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: