poor-man-OS-setup

Generate a comprehensive install.md documentation file for an image dataset. Use when asked to document a dataset, create a dataset readme, or prepare dataset documentation.

Close out an implemented spec by reconciling the project docs with the shipped code (updating them via opus subagents if stale), then removing the resolved spec directory and its INDEX entry so code + up-to-date docs remain the source of truth.

Implement tasks from an approved spec, one at a time, with independent implementer and reviewer subagents per task. The main session acts as orchestrator only.

Bootstrap a new spec under `specs/<feature-name>/` by walking the user through requirements, design, (optional) research, and tasks in EARS/SDD format

Implement items from a TODO file, one at a time, with independent implementer and reviewer subagents per item. The main session acts as orchestrator only.

Scan the project and create initial TODO files organized by area

Prepare a title and description for a GitLab Merge Request from the current branch to main/master, or apply them directly to an existing MR

Adversarially test a design spec's soundness -- is the problem real, the reasoning valid, and the proposed solution correct -- before implementation begins

Adversarially test a TODO file's items -- is each problem real, the reasoning valid, and the proposed fix correct -- before implementation begins

Implement an in-session implementation plan, one step at a time, with independent implementer and reviewer subagents per step. The main session acts as orchestrator only. Use when the user has just drafted a plan (in plan mode or in chat) or pointed at a plan file and now wants it executed step-by-step with an implementer/reviewer loop -- as opposed to ad-hoc coding in the main session.

Resolve in-progress merge, rebase, cherry-pick, or revert conflicts. Inspect repo state, understand each side's intent from commit history, edit files to a correct combined result, verify with build/tests, and finalize the operation.

Adversarial review of a GitLab Merge Request -- raise correctness, edge-case, security, and code-quality issues by reading the diff and, where feasible, running the code.

Generate technical documentation for the project or a specific component

Revise existing documentation to match current codebase state

Create a well-formatted git commit

Analyze existing project documentation for accuracy, completeness, and staleness