# Manage Project State > Maintain .ai/project/state.json (stage and non-secret config references) via projectctl for consistent automation gates. Use when this capability is needed. - Skill: `tomevault-io/manage-project-state` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/manage-project-state` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/manage-project-state/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Security - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/manage-project-state --- # Manage Project State ## Purpose Provide a script-driven workflow to maintain `.ai/project/state.json` as a small, non-secret SSOT for project stage/config. ## When to use Use this skill when you need to: - record the project stage (`prototype`, `mvp`, `production`, ...) - switch context strategy (`contract` vs `snapshot`) - keep CI gates consistent with the intended stage Do NOT use this skill to store secrets (passwords, tokens, private keys). ## Inputs - Stage value: `prototype | mvp | production | maintenance | archived` - Context mode: `contract | snapshot` ## Outputs - Updated `.ai/project/state.json` - A verification result from `projectctl verify` ## Steps 1. Initialize state (idempotent): - `node .ai/scripts/projectctl.js init` 2. Set stage: - `node .ai/scripts/projectctl.js set-stage ` 3. Set context mode: - `node .ai/scripts/projectctl.js set-context-mode ` 4. Verify: - `node .ai/scripts/projectctl.js verify` ## Boundaries - You MUST NOT store secrets in `.ai/project/state.json`. - You SHOULD store only references (for example env var names). - You MUST keep `state.json` schema-valid. ## References - `reference.md` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/willyu1007) — claim your Tome and manage your conversions.