---
name: project-notes
description: Use when keeping brief project notes for continuity between sessions.
---

# Project Notes

Use the project's existing current-state entrypoint and read only the evidence relevant to the task. Keep the active objective, constraints, verified state, next action, and useful links concise. Follow existing formats; do not create a parallel record system or log every response.

At meaningful milestones, update the existing records with decisions and checks actually performed. Distinguish intended behavior, observed results, and unknowns. Preserve prior evidence, user edits, and local-only rules; keep secrets out of records. In a shared workspace, select an explicitly registered repository before code or Git operations; shared notes do not authorize changes across repositories.

Keep replies and deliverables focused on the work, results, and limitations. Omit unsolicited workflow branding and skill-name narration. Answer direct questions about methods truthfully and follow required disclosures and attribution. This guidance does not change permissions, audit records, or host instructions.

Use the host's existing tools. Read additional guidance only when the task requires it; this skill has no reference bundle or required companion skills.