Agent skill · operations · aiskillstore
github-elements-tracking
This skill should be used when the user asks to "track work across sessions", "create an epic", "manage issue waves", "post a checkpoint", "claim an issue", "recover from compaction", "coordinate multiple agents", "update memory bank", "store large documents", or mentions GitHub Issues as persistent memory, multi-session work, context survival, agent collaboration, SERENA MCP memory, or project-level context. Provides complete protocols for using GitHub Issues as permanent memory that survives context exhaustion, with integrated SERENA MCP memory bank for project-level context and large document storage.
Why this skill is useful
Provides complete protocols for using GitHub Issues as permanent memory, including executable report generation scripts and integration with SERENA MCP memory bank.
What it needs
Requires github account access. About 12k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
IRON LAW: User Specifications Are Sacred THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS. 1. Every word the user says is a specification - follow verbatim, no errors, no exceptions 2. Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST 3. Never take initiative to change specifications - your role is to implement, not to reinterpret 4. If you see an error in the spec, you MUST: Stop immediately Explain the potential issue clearly Wait for user guidance before proceeding 5. No silent "improvements" - what seems like an improvement to you may break the user's intent Violation of this law invalidates all work produced. Background Agent Boundaries When running as a background agent, you may ONLY write to: The project directory and its subdirectories The parent directory (for sub-git projects) ~/.claude (for plugin/settings fixes) /tmp Do NOT write outside these locations. --- GHEREPORTS Rule (MANDATORY) ALL agent reports MUST be posted to BOTH locations: 1. GitHub Issue Thread - Full report text (NOT just a link!) 2. GHEREPORTS/ - Same full report text (FLAT structure, no subfolders!) Report naming: <TIMESTAMP><title or description>(<AGENT>).md Timestamp format: YYYYMMDDHHMMSSTimezone Examples: 20251206143000GMT+01epic15wavelaunched(Athena).md 20251206143022GMT+01issue42devcomplete(Hephaestus).md 20251206150000GMT+01issue42testspassed(Artemis).md 20251206160000GMT+01issue42reviewcomplete(Hera).md ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus REQUIREMENTS/ is SEPARATE - permanent design documents with legal validity, NEVER deleted. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/github-elements-tracking