القائمة
Manage tracked feature work with `.ai/current-work.md`, handoffs, and archive rules.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement a bounded code change from a request, spec, or implementation plan. Use when executing implementation work and choosing between quick, bounded, and tracked modes.
Turn a bounded functional spec into an implementation plan. Use when architecture, code structure, sequencing, migration, and verification must be decided before implementation.
Turn current context into a concise implementation spec. Use when a user wants to define what to build, capture requirements, or create a bounded technical/product spec before implementation.
Map a large or unclear initiative into facts, decisions, open frontier, and next work without writing a spec or implementation plan. Use when scope, architecture, dependencies, or sequencing are still genuinely uncertain before creating a spec.
Collapses deterministic multi-step repository research, aggregation, indexing, validation, and transformation into one small purpose-built local script and one Bash run. Use when a task would otherwise require 6+ related read/search/tool calls, iterates over many files or records, cross-references results, or requests batch analysis; do not use for small exploration or broad mutations.
Create a concise ADR for a durable, consequential architectural decision.
| name | project-memory |
| description | Manage tracked feature work with `.ai/current-work.md`, handoffs, and archive rules. |
| compatibility | {"tools":"bash, read, write, edit"} |
Use only for resumable feature work, handoffs, or explicit tracked artifacts.
.ai/current-work.md is an active restart pointer, not a transcript, plan, or evidence warehouse. Keep exactly one active top-level anchor. Linked artifacts hold detail:
.ai/current-work.md
.ai/<slug>-wayfinder.md
.ai/<slug>-spec.md
.ai/<slug>-plan.md
.ai/<slug>-review.md
.ai/archive/
Track only when work spans sessions, has expensive restart/handoff cost, creates durable artifacts, or user asks. Never replace an anchor for another feature without user confirmation.
git rev-parse --show-toplevel 2>/dev/null || pwd.current-work.md once, then only the linked artifact section needed for the active phase.Do not reread or update the anchor for routine worker completion.
Keep under 500 tokens when possible. Shorter is better when restart state remains complete.
# [Feature title]
- **Slug**: <slug>
- **Status**: In progress | Blocked | Done | Idle
- **Updated**: YYYY-MM-DD
## Objective
[1-3 sentences]
## Active artifacts
- `<path>` — purpose
## Major phases
- [ ] [phase + acceptance evidence]
- [ ] User confirmed feature complete
- [ ] Active artifacts archived
## Key decisions
- [Decision] — rationale — Evidence: `<path>`
## Current state
[Active phase, verified result, or blocker]
## Next restart step
[One exact action]
## Open blockers
- [Blocker] — decision needed
Rules:
Update only at a material phase boundary, verified decision, blocker, handoff, or explicit closeout. Batch child results into one verified state packet. The packet supplies: phase, artifacts, acceptance/eval evidence when available, decision/blocker, current state, exact next action, and orchestration budget used when delegated work occurred.
If evidence is unavailable because work blocked before its gate, record that fact. Otherwise, if the packet is incomplete, return a blocker. Do not infer facts.
Archive only after explicit user confirmation. Mark confirmation and archive state, then archive dated snapshots under .ai/archive/.
Verify anchor supports a cold restart without carrying a transcript: objective, active phase, artifact paths, verified current state, blocker, and exact next step.