update-md
Skill0 starsChanged 22 days agoMITView on GitHub
Update project Markdown documentation from actual progress when the user says update md, update docs, save progress, update tasks, update context, update project md, record today's work or write progress.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/setup-project-context/templates/CLAUDE.mdCLAUDE.md
- backend-architectureSkill
- build-review-loopSkill
- capability-intakeSkill
- competitor-market-analysisSkill
- context-auditSkill
- data-analysis-insightsSkill
- data-privacy-securitySkill
- dev-agentsSkill
- dev-patternsSkill
- frontend-system-designSkill
- idea-validatorSkill
- intellectual-property-licensingSkill
- international-legal-researchSkill
- legal-document-drafterSkill
- llm-councilSkill
- make-slidesSkill
- password-authentication-securitySkill
- privacy-data-protection-lawSkill
- project-estimation-planningSkill
- project-startSkill
- rea-researchSkill
- requirements-business-analystSkill
- secrets-credential-managerSkill
- seo-tech-stackSkill
- setup-project-contextSkill
- shopify-ui-auditSkill
- site-incidentSkill
- sop-process-builderSkill
- task-dispatchSkill
- technical-feasibilitySkill
- tech-research-intelligenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 16 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Update only relevant project Markdown documentation using actual completed work, actual changed files and actual verification results.
- Distinctive: line 17
Use this workflow when the user says:
- Distinctive: line 18
update md / update docs / save progress / update tasks
- Distinctive: line 19
update context / update project md / record today's work
- Distinctive: line 20
write progress / update markdown / save current status
- Very specific: line 26
Do not use task-dispatch.
- Distinctive: line 27
Do not invoke agents, MCP servers, plugins, or unrelated skills.
- Distinctive: line 28
Do not perform new application work unless separately requested.
- Very specific: line 36
Read the project index (CLAUDE.md, or .claude/CLAUDE.md in a repo with a remote) only if not already read in current context.
- Distinctive: line 44
Read only the documentation files needed for the update.
- Very specific: line 73
Never recreate legacy files (tasks.md, context.md, memory.md, rule.md, docs/deploy.md…) in a v2 project.
- Distinctive: line 96
Do not write assumed completion.
- Distinctive: line 97
Do not mark tasks complete without implementation evidence.
- Distinctive: line 98
Do not claim tests passed unless performed.
- Distinctive: line 99
Do not write planned testing as completed testing.
- Distinctive: line 100
Do not write long narrative progress summaries.
- Very specific: line 101
Do not place ordinary progress inside CLAUDE.md, rule.md or docs/06-AGENTS.md.
- Distinctive: line 102
Do not update unrelated project documentation.
- Distinctive: line 103
Do not copy private cross-project data into Markdown.
- Distinctive: line 104
Do not record push, tag, release or deployment unless it actually happened.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update Project Markdown from Actual Progress
Request details: $ARGUMENTS
Purpose
Update only relevant project Markdown documentation using actual completed work, actual changed files and actual verification results.
Activation Phrases
Use this workflow when the user says:
- update md / update docs / save progress / update tasks
- update context / update project md / record today's work
- write progress / update markdown / save current status
Mandatory Restriction
For this request:
- Use
update-mdonly. - Do not use
task-dispatch. - Do not invoke agents, MCP servers, plugins, or unrelated skills.
- Do not perform new application work unless separately requested.
- Project docs stay on this machine: never stage, commit or push
CLAUDE.md,.claude/CLAUDE.md,AGENTS.md,AGENTS.local.md,docs/NN-*.md,docs/*.local.md,docs/ref/or.claude/skills/in a repo with a remote (there the index is.claude/CLAUDE.md). Ifgit statuslists one, add the exclude block (~/.claude/references/project-docs-standard.md§7) to.git/info/excludeinstead.
Mandatory Inspection Before Writing
Before updating Markdown:
- Identify the active project root.
- Read the project index (
CLAUDE.md, or.claude/CLAUDE.mdin a repo with a remote) only if not already read in current context. - Inspect actual current progress using:
- Work completed in the current session.
- Files changed in the current session.
git status --shortgit diff --stat- Relevant
git diffoutput only where needed. - Build, lint, test, browser or manual verification actually performed.
- Read only the documentation files needed for the update.
File Selection Rules
v2 projects (the index has ## Docs map)
| Actual Situation | File to Update |
| Task added, started, blocked, waiting or phase changed | docs/08-IMPLEMENTATION.md |
| Session checkpoint (done · next · open decisions) | docs/08-IMPLEMENTATION.local.md §Checkpoint (overwrite, ≤10 lines) |
| Merged, shipped or released | docs/17-CHANGELOG.md (newest first) — and remove the item from 08 |
| Approved scope changed or deliverable status changed | docs/01-PRD.md §Scope / §Scope status |
| UI or design decision | docs/02-DESIGN.md |
| Structure or technical decision | docs/03-ARCHITECTURE.md (§Decisions: - YYYY-MM-DD — decision — why) |
| Schema or migration process | docs/04-DATABASE.md |
| Endpoint, server action or webhook | docs/05-API.md |
| How agents should work on this project, project skill added | docs/06-AGENTS.md |
| Client, URL, environment or access pointer | docs/07-README.md (sensitive → .local.md) |
| Setup steps or env var names | docs/09-SETUP.md |
| Feature specced, built or retired | docs/10-FEATURES.md |
| Auth, roles or security rule | docs/11-AUTH-SECURITY.md |
| MCP / AI tooling for this project | docs/12-MCP.md |
| Third-party service or tracking ID | docs/13-INTEGRATIONS.md |
| Test setup or QA checklist | docs/14-TESTING-QA.md |
| Reusable debugging lesson | docs/15-DEBUGGING.md (### symptom · Cause · Fix) |
| Deployment process or release policy | docs/16-DEPLOYMENT.md |
| Hard rule, stack, commands, or a slot created | the index — CLAUDE.md / .claude/CLAUDE.md (keep ≤70 lines; update the Docs map) |
- Slot marked
unwrittenand the work touched that area: create it now — facts from the code only, each section endingSource: `path`(standard:~/.claude/references/project-docs-standard.md). Remove theunwrittenmarker. - Never recreate legacy files (
tasks.md,context.md,memory.md,rule.md,docs/deploy.md…) in a v2 project.
Legacy projects (no Docs map)
| Actual Situation | File to Update |
| Active task changed, completed or replaced | docs/task.md |
| New pending item, blocker or approval wait | docs/pending.md |
| Approved scope changed | docs/scope.md |
| Proposal or commercial commitment formally changed | docs/proposal.md |
| Approved deliverable completion status changed | docs/completed-vs-scope.md |
| Meaningful completed implementation change | docs/changelog.md |
| Deployment process or release policy changed | docs/deploy.md |
| Confirmed release, push, tag or deployment completed | docs/changelog.md |
| Meaningful technical implementation state changed | context.md |
| Reusable UI or design decision changed | DESIGN.md |
| Reusable debugging lesson found | memory.md |
| Architecture or specification-level rule changed | spec.md |
| Project operating instructions changed | the index (CLAUDE.md / .claude/CLAUDE.md) |
| Permanent unique project hard rule changed | rule.md |
Never Do This
- Do not write assumed completion.
- Do not mark tasks complete without implementation evidence.
- Do not claim tests passed unless performed.
- Do not write planned testing as completed testing.
- Do not write long narrative progress summaries.
- Do not place ordinary progress inside
CLAUDE.md,rule.mdordocs/06-AGENTS.md. - Do not update unrelated project documentation.
- Do not copy private cross-project data into Markdown.
- Do not record push, tag, release or deployment unless it actually happened.
Required Progress Format
## YYYY-MM-DD . <Short Task Name>
- Done: <Actual completed work. Maximum 2 lines.>
- Test: <Actual verification completed, or `Not tested yet`. Maximum 2 lines.>
- Next: <Pending step only when required. Maximum 2 lines.>For several related completed items:
## YYYY-MM-DD . Progress Update
- Done: <First actual completed item. Maximum 2 lines.>
- Done: <Second actual completed item. Maximum 2 lines.>
- Test: <Actual verification completed, or `Not tested yet`. Maximum 2 lines.>
- Next: <Pending step only when required. Maximum 2 lines.>Changelog Format
## YYYY-MM-DD . <Short Change Title>
- Changed: <Confirmed completed change. Maximum 2 lines.>
- Test: <Actual verification performed, or `Not tested yet`. Maximum 2 lines.>
- Reference: <Scope item or affected feature only when useful. Maximum 1 line.>Release Changelog Format
## YYYY-MM-DD . Release <version-or-short-title>
- Changed: <Confirmed released change. Maximum 2 lines.>
- Test: <Actual deployment or post-release verification. Maximum 2 lines.>
- Release: <Actual branch and tag only when used. Maximum 1 line.>Completion Response
Respond only with:
Updated:
- <file path>: <short description>
Recorded:
- Done: <one line>
- Test: <one line>
- Next: <one line only when applicable>
Git Summary:
- Modified documentation files: <file paths>
- Application source files modified: <None, unless separate user-requested implementation>
- Uncommitted changes detected: <yes/no based on actual git status>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

