project-contextlisted

# Project Context Skill Maintains `PROJECT_CONTEXT.md` in the target app repository: a concise map that prevents future agents from rereading the whole repository. It is not a code dump, not a Git history, not a feature archive, not a task tracker. ## When to Use - During `init` when `PROJECT_CONTEXT.md` is missing → first-time analysis ([references/full-project-analysis.md](references/full-project-analysis.md)). - During `init` or `start` when it exists → incremental analysis ([references/incremental-analysis.md](references/incremental-analysis.md)). - During finalization when the approved task changed architecture or navigation → content update per ([references/context-update-rules.md](references/context-update-rules.md)). ## Inputs - Target app repository root (from `bin/frappe-workflow detect --json`). - Template: `templates/project/PROJECT_CONTEXT.md` (plugin root). - Current HEAD (`git rev-parse HEAD`) and, for incremental runs, the recorded `analyzed_commit`. ## Outputs - `PROJECT_CONTEXT.md` at the app repository root, passing `bin/frappe-workflow validate project-context`. - Frontmatter with `analyzed_commit` set to the commit that was analyzed. ## Preconditions - Detection succeeded; the app root is a Git repository. - For incremental runs: existing file parses (frontmatter present). ## Stopping Conditions - Validation passes and `analyzed_commit` equals current HEAD → done. - The repository has no commits yet → record that, produce the struct