epic-tracker
Manages the delivery lifecycle from epic planning through story tracking to implementation handoff. 5 artifact types: Epic, Story, Bug, Issue, Release. Tracker-first when configured (Linear, GitHub Issues/Projects, Jira) via MCP or CLI — artifacts go directly to the tracker with no local files. Falls back to markdown as source of truth when no tracker is configured. Triggers: "create epic", "new epic", "create story", "new story", "edit story", "create issue", "report bug", "create release", "update status", "show roadmap", "list epics", "sync to tracker", "push to linear", "push to github", "push to jira", "pull from tracker", "configure tracker", "handoff". Not for implementing a named story with an existing spec, project- wide overview, feature status within a spec, or quick fixes.
What this skill does
# Epic Tracker
Manages the delivery lifecycle with tracker-first integration and
markdown fallback. Plan epics, track stories, report bugs, file issues,
group releases, push to a tracker (via MCP or CLI) when configured, and
hand off to implementation.
## Workflow
```
discover --> create --> sync* --> track --> handoff
^_______| (sync is optional, gated by config)
```
Tracker-first when configured — artifacts go directly to the tracker.
Falls back to markdown when not.
## Triggers
- **Epic** ("create epic", "new epic") → [epic.md](references/epic.md)
- **Story** ("create story", "new story", "add story") →
[story.md](references/story.md)
- **Edit Story** ("edit story", "update story body", "change story") →
[update-story.md](references/update-story.md)
- **Bug** ("create bug", "report bug", "bug report") →
[bug.md](references/bug.md)
- **Issue / Chore / Task** ("create issue", "new issue", "add issue",
"create chore", "create task") → [issue.md](references/issue.md)
- **Release** ("create release", "new release") →
[release.md](references/release.md)
- **Status / roadmap** ("status", "update status", "mark done", "show
roadmap", "list epics", "overview") → [status.md](references/status.md)
- **Sync** ("sync to tracker", "push to linear/github/jira", "pull from
tracker", "configure tracker") → [sync.md](references/sync.md)
- **Handoff** ("handoff", "implement story", "start story") →
[handoff.md](references/handoff.md)
- **Linear adapter** (auto-loaded by sync) →
[adapters/linear.md](references/adapters/linear.md)
- **GitHub adapter** (auto-loaded by sync) →
[adapters/github.md](references/adapters/github.md)
- **Jira adapter** (auto-loaded by sync) →
[adapters/jira.md](references/adapters/jira.md)
`epic.md` opens with context discovery — reads `.artifacts/docs/prd.md`
and `.artifacts/docs/brief.md` before prompting; falls back to direct
questions when neither file exists.
`status.md` covers both status updates and roadmap reads.
`sync.md` is also auto-loaded by core refs (epic, story, bug, release)
after the artifact is saved when tracker config is present and `kind` is
not `none`.
`adapters/{linear,github,jira}.md` are loaded by `sync.md` based on
`tracker.kind`. Not direct triggers.
`ac-validation.md` is auto-loaded by `story.md` (create) and
`update-story.md` (when AC text changes). Not a direct trigger.
## Guidelines
- Use kebab-case for all artifact and folder names
- Keep each file to a single artifact type in its proper folder
- Save or push immediately after the draft step — no separate preview gate
- Route tracker operations through `sync.md` — core artifact refs stay
tracker-agnostic
- Validate Story AC against ac-validation rules V1-V7 on create and on
edits that change AC text
- Delegate sizing to the implementation phase
## Anti-Pattern: Tracker Operations in Core Refs
Embedding `gh issue create` or Linear MCP calls inside `epic.md`,
`story.md`, etc. couples each ref to a specific tracker. Route tracker
operations through `sync.md` instead — core refs build the artifact, sync
dispatches to the right adapter. Adding a new tracker becomes a new
adapter, not a rewrite of every artifact ref.
## Anti-Pattern: AC Validation on Reads
Validating Acceptance Criteria during pull or roadmap reads breaks
legacy artifacts that predate the Given/When/Then enforcement. Validate
on **write paths only** — story create and edit-when-AC-text-changes —
and let read paths tolerate legacy AC. The implementation consumer
decides how to handle non-conforming AC.
## Anti-Pattern: Mixed Artifact Files
A single file holding both a story and the bugs it spawned, or an epic
mixed with its release plan, makes status updates and tracker pushes
ambiguous. One file = one artifact type. Bugs go to their own file (in
the epic folder or `standalone/`); releases go to `releases/`.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.