projectslisted

# Projects — one operating model, from onboarding to completion Almost every phase of a project's life already has an owner. This skill is the **routing table** over those owners, plus the two things that have no owner today: the **project-switch ritual** and the **per-project artifact checklist**. There is no engine here, and no state anybody sets by hand. A project's state is *read* from its tree — see [state-transitions.md](references/state-transitions.md). ## What this is not for | The task | Its owner | Why not this skill | |---|---|---| | Which item to work on next, what is left to build | `roadmap` | A project's remaining work is items in that project's own roadmap. This skill never ranks or picks. | | Understanding an unfamiliar codebase | `codebase-onboarding`, `repo-scan` | Those own *how* to read a codebase. This skill only says that phase comes first and names them. | | Planning before source is edited | `superplan`, `blueprint` | Plan depth is a shipped standard with its own gate. Nothing here relaxes or restates it. | | Handing work to another session | `/relay`, `successor` | A handoff is a session-level act. A project switch inside one session is not a handoff. | | The project's vocabulary | `domain-modeling` | Terms live in the project's own `CONTEXT.md`, written by that skill. | | Continuing past the item in hand | `endless` | Continuation is about the loop, not about the project. | | Applying this model to a specific project subtree | that project's own