← ClaudeAtlas

goallisted

Drive the current milestone's goal run end-to-end — resolve the milestone from docs/PROGRESS.md (M3 as of this writing), enforce the Architect's sole git authorship and a properly named feature branch before any commit, then loop the /build-package cycle through the milestone's packages and close with /milestone-review. Use when asked to run the milestone, start "the M<x> run", or invoked as /goal.
mertefesensoy/Ephesus · ★ 1 · Code & Development · score 67
Install: claude install-skill mertefesensoy/Ephesus
# Run the current milestone goal You are executing a full milestone run, not a single package. The contract for every step is `BUILD-PROMPT.md`; this skill only adds the run's session mechanics (identity, branching, sequencing). Where they seem to disagree, BUILD-PROMPT wins. ## 0. Session preconditions — before reading anything else 1. **Sole authorship.** Every commit in this repository is authored by the Architect and nobody else: ```bash git config user.name "MERT EFE ŞENSOY" git config user.email "sensoymertefe@gmail.com" ``` Never add `Co-Authored-By`, session, or any identity-bearing trailer; never put a model identifier in a commit message, file, or PR body. This is enforced three ways (ENGINEERING-STANDARDS §2): `.githooks/` refuse the commit, CI's attribution job scans the whole history, and you verify yourself — run `node scripts/check-attribution.cjs` now and after every push. If hooks are unarmed (fresh clone that skipped `npm install`), run `node scripts/arm-hooks.cjs`. 2. **Green baseline.** `npm ci` (or confirm node_modules is current), then `npm run typecheck && npm run lint && node scripts/check-invariants.cjs` must pass before you write a line. A red baseline is a blocker to report, not to absorb. ## 1. Resolve the milestone Open `docs/PROGRESS.md`; the current milestone is the first one with unchecked packages (BUILD-PROMPT's build-state block names it — **M3, resuming at M3.1**, as of 2026-08-27). Read