← ClaudeAtlas

ddalggaklisted

Use when the user wants a Codex App native GitHub issue to implementation to review to recovery workflow, or wants to plan issues, create GitHub issues, inspect status, ship an existing lane, clean up after merge, write retrospectives, improve prompts, or run a one-shot local diff check.
JeremyDev87/ddalggak · ★ 0 · Code & Development · score 66
Install: claude install-skill JeremyDev87/ddalggak
# ddalggak - Codex App workflow Ddalggak is a thin-router skill for one repeated cycle: GitHub Issue -> plan -> parallel implementation -> independent review -> self-healing -> retrospective. The always-loaded `SKILL.md` must stay small enough to route safely; detailed procedure belongs in `references/`, reusable wording belongs in `templates/`, and mechanical regression protection belongs in `scripts/` or future `fixtures/` / `evals/`. ## Subcommands Supported subcommands are: `start|review|status|plan|issue|clean|ship|retro|prompt|check|getwiki|setwiki`. Standard cycle: `prompt` -> `plan` -> `start` -> `ship` -> `review` -> `retro`. `status`, `issue`, `clean`, `check`, `getwiki`, and `setwiki` are supporting commands. ## Hot-Path Target Architecture The hot path is frontmatter, overview, routing invariant, code modification invariant, global non-negotiable guardrails, subcommand dispatch table, required reference map, stop conditions, and verification checklist. Current hot-path target is the semantic subcommand contract, not a stale #94/#95 line-count reminder: each command must expose mode, source-edit boundary, GitHub/write side effects, required references, and stop condition while long procedure stays in references/templates/scripts. ## Reference And Template Map The hot path stays compact. Load these files only when the routed subcommand needs low-frequency detail. After Brain v0 migration/hardening, apply `references/2026-06-04-brain-v0-wiki-authority-in-dd