uchetsai-creator

add-framework-adapter

Use when contributing to project_starter_v5 itself and adding spec↔code drift detection support for a new framework, language, or tool not yet covered by verify_spec_code.py, or adding an entirely new project-type capability. This is for working on the framework repo itself (project_starter_v5) — not for application code in a project that merely uses the framework. Do NOT use this for normal app development tasks.

Code & Development Listed

code-quality-check

Use when reviewing code quality/architecture — during Step 1c of a retrofit, whenever the user explicitly asks for a code quality or architecture review of this project, or when Learning Checkpoint A escalates because the user confirms unfamiliar/inherited/unreviewed code needs a full review. Checks layering, Package First, complexity, naming, schema, security, error handling, observability, permission consistency, state machine consistency, interface overlap, synthetic test data, cross-component interfaces, and performance — scored High/Medium/Low/Nit against this project's declared type.

learning-checkpoint

Use before implementing any task, every task, no exceptions — Checkpoint 0 for unfamiliar technology, Checkpoint A before modifying existing code, Checkpoint B before a new feature with no existing code, and Checkpoint C always before closeout. This is live discussion during the task, not a file to write and defer. After reading this, also read guidance/learning-checkpoints/<the project's declared type>.md for the type-specific angle on the same checkpoints.

module-completion-check

Use only when a module has just been confirmed 100% complete (all its tasks are marked done in docs/project-plan.md) — inserts logger calls per logging-spec.md, offers optional debug instrumentation, and decides whether to rebuild the PDF. Do NOT use mid-module, and do NOT use for ordinary per-task closeout (see task-closeout instead).

Data & Documents Listed

retrofit-existing-project

Use when documenting an existing codebase that already has code but no docs — retrofitting project_starter documentation onto it. Walks through reading the codebase, running the module inventory scan, a code quality check, filling in architecture/spec/business docs, module flow files, project status docs, and generating the PDF. Do NOT use for a brand-new project with no code yet — use the per-type init file instead (see AGENTS.md → Project Initialization).

task-closeout

Use at the end of every task, once all Steps and Verify in docs/current-state.md pass, when the inline Closeout section in current-state.md isn't enough on its own — e.g. you need the full verification table, the exact per-artifact-type verification method, or the commit-sequencing note for step 1c (promoting Next Task -> Current Task). For the common case, current-state.md's own Closeout section already has enough detail and this Skill isn't needed. Do NOT use for module completion (all tasks in a module done — see module-completion-check) or sprint documentation sync (3 pending sprint-change-log.md entries — see sprint-doc-sync).