القائمة
Use when Claude forgets context or hallucinates during the same session. Re-reads task-flow skill and task files to get back on track. Say "ar-taskflow-remember" or "remember".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Record an improvement, learning, fix, or refinement to the Agentic Repos framework. Invoke when a new pattern emerges, a bug is found in a skill/agent/rule, or a workflow refinement is identified during work. Handles version bumping, CHANGELOG updates, and cross-file consistency. Also user-invocable via "ar-add-improvement" or "update framework".
Install or update context-processing skills (discussion, email, meeting, specs, state) into a Docs Project. Separate from ar-taskflow - does not touch ar-taskflow skills or config.
Adopt Agentic Repos in a project, writing its per-repo config + rules layer by extracting the codebase's real conventions. Say "ar-install" or "make this repo agent-ready".
Install or refresh the global Agentic Repos layer on this machine (ar-* skills, scripts, session hook, default-branch guard). Say "ar-install-tools" or "setup tools".
Reviews a PULL REQUEST of the Agentic Repos framework SOURCE repo itself for project-based noise. Its input is a framework PR, on trigger it FIRST asks which agentic-repos PR to review (framework PRs only; it refuses PRs from any other repo). Proves the PR introduces ZERO project-based noise into the project-agnostic framework, installed artifacts (rules/, skills/, agents/, templates/, setup.md) AND docs/. Catches a source project's identity (real names, packages, developer paths, tickets, people, dated incident notes), whole files bound to one project (a <project>-feedback.md mining doc, anything named after or dominated by a single product line, these belong in the source project, not the framework), stack idioms leaking into stack-agnostic skill/agent bodies, ungenericized business-domain examples, rationale/version-history bloat, mis-tiered rules, and version-file drift. Use whenever you want to review/self-review an agentic-repos PR for "does this leak or bind a project into the generic framework," befor
Refresh an adopted project's per-repo config + rules layer to the current framework version. Say "ar-upgrade" or "refresh the project rules".
| name | ar-taskflow-remember |
| description | Use when Claude forgets context or hallucinates during the same session. Re-reads task-flow skill and task files to get back on track. Say "ar-taskflow-remember" or "remember". |
| disable-model-invocation | true |
Quick context recovery when Claude loses track during the same session.
Follow the rule at <standards_location>/learning-routing.md (resolve standards_location from .claude/config_hints.json): route any learning to a project rule (docs/ai-rules/), a framework improvement (ar-record-improvement), or conversational-only, never personal auto-memory.
Use this skill when:
Use ar-taskflow-resume instead when:
Trigger: User says "ar-taskflow-remember" or "remember"
Re-read ar-taskflow skill first:
~/.claude/skills/ar-taskflow/SKILL.md) to refresh on the workflowGet task folder path:
Read task files in priority order:
execution-summary.md (MUST read - source of truth for current state)execution_plan.md (SHOULD read - shows what we're building)prompt-understanding.md (only if needed for clarity)Check git branch:
git branch --show-current
Present brief summary:
✅ Back on track.
Task: {task folder name}
Phase: {from execution-summary}
Branch: {current branch}
Last Action: {from execution-summary}
Next: {from execution-summary or infer from phase using ar-taskflow knowledge}
Ready to continue. What would you like me to do?
Wait for user direction - Let ar-taskflow workflow handle what comes next