project-status-maintenance
Maintain or create PROJECT_STATUS.md files at the repository root with the canonical structure (Executive Summary, Completed Components, In Progress, Next Steps, Known Issues, Notes). Use when starting or finishing work on a project, when the user asks to update or create PROJECT_STATUS.md, when a session involves significant changes that should be reflected in the project status file, or when reviewing project state before committing.
- License 许可
- Unlicense
- 所属仓库
- saski/arnesto
- 最近更新
- 2026-11-12
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- project-status-maintenance
- description
- Maintain or create PROJECT_STATUS.md files at the repository root with the canonical structure (Executive Summary, Completed Components, In Progress, Next Steps, Known Issues, Notes). Use when starting or finishing work on a project, when the user asks to update or create PROJECT_STATUS.md, when a session involves significant changes that should be reflected in the project status file, or when reviewing project state before committing.
03 SKILL.md 正文
Project Status Maintenance
Every active project repository should maintain a PROJECT_STATUS.md at the root level. It is a living document tracking current state, completed work, and next steps.
When to update
Update PROJECT_STATUS.md after any significant change: new features, bug fixes, tests added, dependencies changed, documentation modified, project structure changes. Do not let it drift — outdated status files are worse than no file.
Canonical template
Use this structure when creating or rewriting PROJECT_STATUS.md:
# [Project Name] - Project Status
**Last Updated**: YYYY-MM-DD
**Overall Status**: [Status Emoji] **[Percentage]% Complete** - [Brief Status]
---
## Executive Summary
| Component | Status | Progress | Blocking |
|-----------|--------|----------|----------|
| Component 1 | ✅ Complete | 100% | - |
| Component 2 | 🟡 In Progress | 50% | - |
| Component 3 | ⚠️ Pending | 0% | No |
**Current Readiness**: [Status] - [Brief description]
---
## ✅ Completed Components
[List of completed work with dates and details]
---
## 🚧 In Progress
[Current work items with progress indicators]
---
## 📋 Next Steps
1. [First priority task]
2. [Second priority task]
3. [Third priority task]
---
## 🐛 Known Issues
[Any known bugs or limitations]
---
## 📝 Notes
[Additional context, decisions, or important information]
Status indicators
Use consistent indicators across the file:
- ✅ Complete — finished and tested
- 🟡 In Progress — actively being worked on
- ⚠️ Pending — planned but not started
- 🟢 Ready — ready for next phase
- 🔴 Blocked — blocked by dependencies or issues
- ❌ Cancelled — planned but cancelled
Update process
- Update the Last Updated date.
- Refresh the Overall Status percentage and brief description.
- Move items from In Progress to Completed Components when done.
- Update progress percentages for in-progress work.
- Revise Next Steps based on current priorities.
- Add any new issues to Known Issues.
- Document significant decisions in Notes.
Best practices
- Be specific: include dates, commit hashes, or PR numbers when relevant.
- Be honest: do not inflate progress percentages.
- Be actionable: next steps should be clear and prioritized.
- Be concise: keep it readable, not exhaustive.
- Be current: update regularly, not only at milestones.
Anti-patterns
- Creating the file but never updating it.
- Using vague status descriptions.
- Forgetting to update the Last Updated date.
- Leaving stale information in the file.
- Making the file too verbose or too sparse.
Integration with workflow
- Before starting work: review
PROJECT_STATUS.mdto understand current state. - During work: update status as progress is made.
- Before committing: ensure
PROJECT_STATUS.mdreflects the changes in the commit.
04 同仓库更多 Skills
visualize
Use /visualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.
update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
update-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
statusline
Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
shell
Runs the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.