Plans

APC may store durable project plans when they are safe to share and useful beyond one session.

Location

.apc/plans/

Examples:

.apc/plans/auth-migration.md
.apc/plans/release-hardening.md
.apc/plans/cursor-checkout-flow.md

What belongs in plans

Good APC plans contain:

• implementation plans approved or useful for future work
• migration plans
• release plans
• investigation summaries with next steps
• open decisions and constraints

Do not store:

• private scratch notes
• raw chat plans copied from a session
• customer data
• credentials
• local-only task state
• model reasoning traces

Recommended shape

---
title: Auth migration
status: active
owner: architect
updated: 2026-06-08
---
 
# Auth migration
 
## Goal
- Move token validation to the gateway.
 
## Constraints
- Preserve existing session cookies during migration.
 
## Steps
- Add gateway validation middleware.
- Add compatibility tests.
- Remove duplicate service-level checks after rollout.

Relationship to Cursor plans

Cursor or another IDE may create planning artifacts during work. If a plan becomes project-owned, safe, and durable, copy or translate it into .apc/plans/. Keep transient planning UI state and session scratch work in the runtime that created it.

APC is the project source. Tool-specific files may still exist as projections when a runtime needs them.