Cursor rule Cursor
Generic wrapper for any ad-hoc implementation request that doesn't match a specific workflow (develop-feature, fix-tech-debt, hotfix). Ensures pre-flight, planning, and task-completion happen for every task — not just named workflows.
Cursor rule Cursor
When Knowledge Bus entries are older than 30 days, or memory files have accumulated stale content. Run monthly or when bus/ is cluttered.
Cursor rule Cursor
When deciding where to store a piece of knowledge (memory files vs Confluence vs Jira). Use when about to document something, capture a lesson, create a ticket, or publish a decision.
Cursor rule Cursor
When checking feature parity across platforms after shipping a feature, receiving a Knowledge Bus alert, or on a scheduled cadence. Requires a blueprint with a parity matrix.
Cursor rule Cursor
When the user has made an architectural decision that needs to be recorded. Use when ending a brainstorm session or finishing develop-feature Phase 1 with a significant architectural choice that should be written up as an ADR, published to Confluence, and cross-linked from LESSONS.md.
Cursor rule Cursor
When a production incident has been resolved and needs a written post-mortem. Use after the hotfix workflow completes, to publish a structured post-mortem to Confluence, optionally create Jira tickets for action items, and cross-link findings from LESSONS.md.
Cursor rule Cursor
When restructuring, renaming, or reorganising existing code without changing its external behavior. Use instead of develop-feature when no new functionality is being added.
Cursor rule Cursor
When someone leaves the team or rotates off the project. Use when you need to mark a member inactive (or delete them outright) in .memory/TEAM.md and reassign any ownership or escalation responsibilities they held.
Cursor rule Cursor
When removing a platform from the workspace dispatcher. Does NOT delete the subdir or its agentskel install — only unregisters it from workspace config and AGENTS.md.
Cursor rule Cursor
Session initialization procedure. Checks memory mount, reads all required memory files, validates skeleton version, checks dependency freshness, and surfaces alerts. Must be executed at the start of every session before any other work.
Cursor rule Cursor
When the user needs to configure Confluence integration for this project. Use when wiring up the Atlassian MCP to .memory/CONFIG.md so ADRs, runbooks, postmortems, and specs can be auto-published to the right space and parent pages.
Cursor rule Cursor
When the team needs to configure Jira integration for agentskel. Use when populating .memory/JIRAWORKFLOW.md and the Jira section of .memory/CONFIG.md by introspecting the Jira project through Atlassian MCP.
Cursor rule Cursor
When setting up agentskel on a project for the first time. Run once per project to install memory, rules, skills, workflows, entry points, and standards.
Cursor rule Cursor
When bootstrapping a project's team roster. Use when .memory/TEAM.md has not yet been populated and you need to establish members, roles, ownership, and escalation contacts for the first time.
Cursor rule Cursor
When setting up agentskel as a workspace dispatcher — multiple independent projects under one parent folder, each with its own git repo. Run once at the workspace root to create routing dispatcher files. Does NOT install agentskel in subdirs.
Cursor rule Cursor
When creating a new skill or workflow, or improving an existing skill's effectiveness. Use when the user asks to add a capability, write a new workflow, or when a skill isn't triggering or being followed reliably.
Cursor rule Cursor
When delegating work to a subagent — implementation, review, research, or exploration. Use when a task benefits from a fresh context window, parallel execution, or isolated scope.
Cursor rule Cursor
When skeleton version in CONFIG.md is behind the current agentskel VERSION. Run by tech lead to apply upstream skeleton improvements to a project. Changes go through a PR — never directly to the default branch.
Cursor rule Cursor
When the GitHub team and .memory/TEAM.md have drifted. Use when you suspect new joiners, leavers, or rotations have happened on GitHub but TEAM.md hasn't been updated, and you want a diff-and-reconcile pass rather than editing member-by-member.
Cursor rule Cursor
When actual project dependency versions may have drifted from VERSIONS.md. Run after dependency upgrades or when VERSIONS.md looks stale.
Cursor rule Cursor
When workspace dispatcher templates have changed in a newer skeleton version. Regenerates dispatcher files at the workspace root while preserving the workspace name, platforms list, and blueprint path from config.
Cursor rule Cursor
When applying debugging techniques during any investigation — root cause tracing, bisect, defense-in-depth. Enforces hypothesis-first analysis and prohibits guess-and-check changes. Use standalone or inside the debug-issue workflow.
Cursor rule Cursor
Post-task checklist for CHANGELOG, TIMELOG, SYMBOLS/MAP, RESUME, and memory commits. Execute after completing a task that modified files outside .memory/. Do NOT run for pure discussion, memory-only maintenance, or skeleton syncs.
Cursor rule Cursor
When decomposing a feature or spec into implementable subtasks, estimating scope, or orchestrating multi-step work across subagents.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: