Development Process

Anuva development is driven from interactive Codex App tasks. A workflow prompt states the intent, a Codex skill applies reusable judgment, and the Anuva CLI performs named operations against Linear, Git/GitHub, docs servers, local services, and Cloudflare Tunnel.

Workflows

1. Plan Product Change
2. Implement Linear Issue
3. Review and Complete PR

Operating references

• Anuva Development Process Policy
• Anuva Development Policy Implementation Plan
• Anuva Development Policy Phase 2 Implementation Plan
• Anuva Development Policy Phase 3 Implementation Plan
• Anuva Development Policy Phase 4 Implementation Plan
• Anuva Development Policy Phase 5 Implementation Plan
• Anuva Development Policy Phase 6 Implementation Plan
• Anuva Development Policy Phase 7 Implementation Plan
• Sources of Truth
• Documentation Lifecycle
• Development Environment and Tunnels
• Windows Development Machine Bootstrap
• Cloudflare Tunnel and Access Setup
• Implementation Repository Changes
• One-Time Bootstrap Workflow Repair

The development policy is the target high-level source of truth. During its phased rollout, current checked-in skills, CLI commands, and strict documentation verification remain operative unless a completed phase explicitly replaces them.