worklisted

Lead implementer: use the docs router to load the active task and its context chain, pick or receive the next incomplete task, implement it under project conventions, then cross-provider adversarially verify the diff. Use to resume roadmap work, start or continue a task, implement the next item, or as flow stage 2. In flow mode the interview is skipped and doc mutation is left to librarian.
supermodo/skills · ★ 1 · AI & Automation · score 74

Install: claude install-skill supermodo/skills

# work — lead implementer > **Requires:** the sibling `protocols` skill (shared protocol masters) and a valid `skills.config.json` (create with the `config` skill). Missing either → halt with that exact pointer; never guess. Pick up the next task, build the right team, drive it to completion, and get it independently verified. Start at the docs router; project constraints come from docs, not from this file. Read `../protocols/references/docs-convention.md`, `../protocols/references/questions.md`, `../protocols/references/cross-model.md`, `../protocols/references/adversarial-review.md`, `../protocols/references/handoff.md`, `../protocols/references/reports.md`. Validate config FIRST per the config contract — halt on missing/invalid config, naming the field, point at `config`. **Never mutate git** (no commit/merge/rebase/push). > **Cross-tool note (Claude Code ↔ Codex).** Written in Claude Code idioms. > Under Codex, translate: `$ARGUMENTS` = the invocation argument; the `Agent` > tool with `subagent_type = <file>` = dispatch the matching agent from the > config `agents.dir` roster (same roles mirrored per host, e.g. > `.codex/agents/*` alongside `.claude/agents/*`); "use AskUserQuestion" = ask > in chat. If a role has no host-native agent file, read that role's > definition and apply its checklist inline. ## Step 1 — detect current state Read the router (`docs.entry`, default `docs/README.md`) before following any doc path. Resolve the active program/initiative and the n