agentic-project-memorylisted

Maintain durable project memory and assign each kind of information to one authoritative location across sessions, agents, GitHub Issues, milestones, pull requests, and source-of-truth repository documentation. Use when creating or updating a handoff; deciding whether information belongs in an Issue, PR, spec, roadmap, changelog, task file, practices catalogue, retrospective, FAQ, or pending lessons; deciding where a deferred idea is recorded; reconciling documentation drift; reconciling which documents a completed phase must update; preserving session continuity; documenting tooling failures; splitting an oversized internal document; or defining documentation-impact accounting. Do not use for ordinary GitHub Issue or PR operations that do not affect project memory or source-of-truth boundaries, or for writing ordinary reference documentation -- a README, API docs, docstrings -- that carries no source-of-truth status.
gidde032/agentic-workflow · ★ 0 · AI & Automation · score 63

Install: claude install-skill gidde032/agentic-workflow

# Agentic Project Memory The portable architecture for keeping a project coherent across sessions, agents, GitHub delivery cycles, and releases. It separates immediate state, durable planning, delivery history, public documentation, and workflow rationale so that no agent must reread several overlapping documents to discover what is true. Worked examples and provenance: `examples.md`. --- ## When NOT to use this skill | If you need… | Go to… | |---|---| | Cost and model-mixing strategy | `agentic-session-economics` | | How to run review passes | `agentic-review-orchestration` | | Regression tests and quality gates | `agentic-verification-discipline` | | Human checkpoints and slice cadence | `agentic-collaboration-cadence` | | Phase structure and living spec | `agentic-phase-workflow` | | Day-one instantiation on a new project | `agentic-project-bootstrap` | | Creating, editing, or triaging an ordinary Issue or PR without changing memory boundaries | Use the available GitHub tooling directly | | Performing a repository-wide documentation and GitHub migration | Use the explicit migration workflow when it has been deliberately invoked; do not infer migration from normal project work | | Configuring Actions checks or diagnosing CI failures | `agentic-verification-discipline` or the relevant GitHub CI workflow | --- ## 1. The Four-File Memory Architecture and GitHub Delivery Layer Most projects collapse operating rules, current state, planning, delivery history, rationale,