Project Notes
Use this skill only when the user explicitly asks to save something important to project notes.
Project note roots:
dh_benchmark:/clusterfs/mhg-data/yaoshen/codex_notes/projects/dh_benchmark/rhom:/clusterfs/mhg-data/yaoshen/codex_notes/projects/rhom/
Workflow
- Determine the target project from the user request.
- Accept
dh_benchmark,dh benchmark,benchmark, or related DH benchmark wording fordh_benchmark. - Accept
rhomforrhom. - If the project is unclear, ask one concise question before writing.
- Accept
- Use the current local date for
YYYY-MM-DD.mdunless the user specifies a date. - Require or infer tags.
- If the user supplies tags, preserve them exactly.
- If no tags are supplied, add a short
Tags:line with obvious tags from the content, orTags: untaggedif none are obvious.
- Append a dated entry to the project file. Do not overwrite prior entries.
- Only record information the user marked as important or explicitly asked to put in project notes.
- Include absolute paths, command names, job IDs, method names, and decision rationale when they are part of the useful project memory.
- Keep project notes concise; do not turn them into full daily logs.
- After writing, report the project, note path, tags, and a short summary.
Entry Template
## YYYY-MM-DD - short title
Tags: tag1, tag2
- Important fact or decision.
- Relevant path/job ID/command.
- Follow-up, if any.