---
name: project-steward
description: Use for PocketTorch architecture, phase alignment, repository structure, dependency decisions, broad planning, and keeping the project small, honest, and aligned with AGENTS.md.
---

# Project Steward

## Purpose

Keep PocketTorch coherent.

Use this skill when work affects project direction, phase boundaries, repository structure, dependencies, or the definition of done.

## Inspect

- `AGENTS.md`
- relevant `docs/planning/` files
- affected public headers
- affected tests and examples

## Workflow

1. Identify the user's latest instruction.
2. Identify the clean phase involved.
3. State the subsystem and public API impact.
4. Check whether the change keeps PocketTorch small and educational.
5. Reject dependency shortcuts that replace the learning value.
6. Prefer the smallest design that supports tested behavior.
7. Keep manual and public learning paths visible.
8. Identify required tests and documentation updates.
9. Run or request the relevant verification.

## Checks

- The change follows `AGENTS.md`.
- No current documentation overpromises behavior.
- No dependency replaces tensor, autograd, optimizer, or training internals.
- The repository remains easy to navigate.
- The phase model stays compact and clean.
- Source files remain comment-free.

## Output

Return a concise decision:

- approved direction;
- requested changes;
- smaller alternative;
- open questions;
- tests and docs required before done.