agentleFS
Sign inStart free
VoTruongDanhVoTruongDanh/Skills-Agent/.cursor/rules/status.mdc

Skills-Agent / rules

Cursor rule4 starsChanged 33 days agoMITView on GitHub

Project status summary, progress snapshots, repo overview, and outstanding work tracking. Use when the user wants to know where a project stands. Triggers: status, progress, overview, what's done, dự án đang ở đâu, tiến độ, tổng quan.

We split this status.mdc into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    START: Read .ai-memory.md from project root.

    line 10
  2. Very specific:

    END: Update .ai-memory.md using Memory Compaction Rules with: status snapshot, what's working, gaps, risks, and priorities.

    line 11
  3. Distinctive:

    Do not recommend broad refactors without confirming scope.

    line 52
  4. Distinctive:

    Always read and update the memory file.

    line 53
  5. Very specific:

    After completing, read .kiro/skills/_scripts/verify-all.md for full project verification checklist.

    line 56
  6. Very specific:

    All code snippets and example files referenced or produced by this skill must be UTF-8 encoded.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
status.mdc
---
description: "Project status summary, progress snapshots, repo overview, and outstanding work tracking. Use when the user wants to know where a project stands. Triggers: status, progress, overview, what's done, dự án đang ở đâu, tiến độ, tổng quan."
encoding: "UTF-8"
agents: [project-planner, orchestrator]
globs: ""
alwaysApply: false
---

## Memory Protocol
**START**: Read `.ai-memory.md` from project root. This is the PRIMARY source for status — check all recorded history, decisions, tasks, bugs, and milestones.
**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: status snapshot, what's working, gaps, risks, and priorities.

## Goal
Summarize where things stand right now, leveraging the memory file for deep context.

## Agent Routing
- For project health overview → read `.kiro/skills/agents/agents/project-planner.md` and apply its knowledge
- For multi-workstream status → read `.kiro/skills/agents/agents/orchestrator.md` and apply its knowledge
- For technical debt assessment → read the relevant specialist agent file based on domain

## Workflow
1. **Read Memory** — Load `.ai-memory.md` as the primary context source.
2. Inspect the repository, relevant files, and any recent context from the chat.
3. Summarize what already exists.
4. Identify gaps, risks, TODOs, and likely next priorities.
5. Present a concise health/status view.
6. **Update Memory** — Save current status snapshot to `.ai-memory.md`.

## Output format
- Current state (from memory + repo scan)
- What is working
- What is incomplete
- Risks or blockers
- Recent changes (from memory)
- Recommended next step

## Checklist
- [ ] Memory file read for historical context
- [ ] Repository scanned for current state
- [ ] Working features identified
- [ ] Gaps and incomplete items listed
- [ ] Risks or blockers flagged
- [ ] Next priority recommended
- [ ] Memory file updated with status snapshot

- [ ] Clean code chuẩn (Standard clean code applied)
- [ ] Cập nhật đầy đủ tất cả các file liên quan (All related files fully updated)

## Rules
- Be specific and evidence-based.
- Separate facts from inference.
- Do not recommend broad refactors without confirming scope; ASK if the fix would touch many areas.
- Always read and update the memory file.

## Quality Gate
After completing, read `.kiro/skills/_scripts/verify-all.md` for full project verification checklist.

## Related Skills
- `/plan` → read `.kiro/skills/plan/SKILL.md` — Create plan for incomplete items
- `/debug` → read `.kiro/skills/debug/SKILL.md` — Investigate flagged risks
- `/deploy` → read `.kiro/skills/deploy/SKILL.md` — Deploy when ready

## Encoding
All code snippets and example files referenced or produced by this skill must be UTF-8 encoded. When applicable, include `encoding: "UTF-8"` in SKILL.md front-matter and ensure saved files use UTF-8 (no BOM).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free