niels-emmer/myace

niels-emmer/myace

Command

Create a new Alembic database migration for the backend.

niels-emmer/myace

Command

Compile a MyACE profile for a target framework (opencode, claude-code, cursor).

niels-emmer/myace

Command

Run tests across all MyACE components (backend, frontend, CLI).

niels-emmer/myace

Command

Start the full MyACE development environment with Docker Compose.

niels-emmer/myace

Command

Read-only cross-check of spec, plan, and tasks for consistency, duplication, gaps, and constitution violations before implementation starts.

niels-emmer/myace

Command

Systematically find and resolve the highest-impact ambiguities in a spec before planning starts, instead of discovering them mid-implementation.

niels-emmer/myace

Command

Create or update the project's constitution — the small set of non-negotiable product/architecture principles every spec, plan, and implementation must be checked against.

niels-emmer/myace

Command

Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.

niels-emmer/myace

Command

Turn a clarified spec into a concrete technical plan — architecture, data model, and interfaces — before any task breakdown or code.

niels-emmer/myace

Command

Turn a short feature request into a written spec — user-facing behavior and testable acceptance criteria, deliberately free of implementation detail — before any planning starts.

niels-emmer/myace

Command

Turn a plan into an ordered, independently-checkable task list, with every task traceable back to a requirement and every requirement covered by at least one task.

niels-emmer/myace

Command

Pre-deployment evaluation checklist — holdout eval, baseline comparison, leakage scan, failure mode documentation.

niels-emmer/myace

Command

Scaffold a new tracked experiment — create notebook, set up tracking, log baseline, define success criteria.

niels-emmer/myace

Command

Produce a short written plan before implementing anything nontrivial, so the approach is explicit before code starts — and get human approval before any state-changing apply.

niels-emmer/myace

Command

The standard pre-merge verification checklist for infrastructure changes — plan/validate/lint/policy checks, tests, security pass, rollback path, and documentation, all confirmed before a change is considered done.

niels-emmer/myace

Command

Quick pre-ship checklist to run before pushing or merging a change.