Plan, revise, and review Goddard desktop app features using `app/plans/`, `spec/app.md`, `app/best-practices.md`, and `app/glossary.md`. Use when Codex needs to draft a new app feature plan, update or split an existing plan, reconcile a proposed feature with current app constraints, or identify the state modules, components, dependencies, and deferred follow-ons for an app change.
Plan app features as doc changes grounded in the current spec and app architecture. Keep plans tab-first, local-first, thin over shared contracts, and explicit about what is MVP, deferred, or blocked.
app/README.md, app/best-practices.md, and app/glossary.md.spec/README.md and spec/app.md.app/plans/sprints.md and app/plans/feature-recommendations.md.app/plans/ that overlaps the requested feature.app/plans/, in app/plans/feature-recommendations.md, or in a spec discussion because it conflicts with the current product or host model.Goal, Scope, State, Components, Dependencies, Open Questions, and Why now only when they help.RepositoriesPage, SessionLaunchState, or PullRequestView instead of generic module names.app/plans/feature-recommendations.md when the result is intentionally deferred follow-up work.app/plans/sprints.md only when the user explicitly asks for sprint sequencing or when the feature plan cannot stay correct without a matching sprint change.spec/ only when a human explicitly asks. Otherwise call out mismatches instead of editing around them.