land-feature

Review a diff, a plan's implementation, or a plan before execution, for correctness, quality and plan adherence, bucketing findings by severity into…

Translate a spec into a numbered, deterministic implementation plan under specs/.

Iteratively drill a feature, idea or requirement into a locked spec, then hand it to /plan-doc.

Audit the setup as it is actually used — session transcripts, skill/agent/MCP invocation counts, session shape, round-trip waste — and report ranked findings…

Execute a specs/ plan end to end, one step at a time, then hand off to finalize.

Scan the code against four architecture checks — layout, isolation, interface strength, extensibility — and propose specific fixes without applying them.

Note a recurring friction, correction, or workflow pattern during work, for later review as a possible new or improved skill.

Take raw idea notes and adversarially decide whether each should become a skill — fold into an existing one, add as new, or drop — with an in-principle rating.

After a bug is fixed, characterize it as a code pattern and hunt the rest of the codebase for structural twins, ranked by confidence.

Trace and verify every consumer before changing a public signature in src/devkit/ (env.py, db.py, oauth.py, mcpsecurity.py, mcpserver/, bridge/, bootstrap.py).

Compress material into judgment instead of coverage — what a skim would miss, then the three or four points to lead with.

Prepare a branch for merge — done-checks, pre-merge docs, version bump, then a staged conventional commit.