cracking-shells-playbook

Creates, executes, and amends graph-based campaign roadmaps. Use when: (1) planning a campaign or feature rollout as a structured roadmap, (2) authoring leaf tasks and step sequences, (3) executing work via BFS traversal, (4) tracking or updating node status (planned/inprogress/done/blocked), (5) restructuring roadmap nodes, (6) managing amendments, or (7) working with any __roadmap__/ directory.

Guides production of stakeholder-reviewable reports across coding, research, data analysis, and writing work. Use when producing any of these seven report types: (1) observation — peripheral finding for cold-start agent hand-off; (2) findings — data-first results briefing with tables, charts, and steering questions; (3) notice — lightweight improvement idea captured outside current task scope; (4) open-question — open question framing for fresh-agent delegation; (5) architecture — pre-implementation analysis with diagrams, contracts, and risk register; (6) test-definition — risk-driven test plan with test matrix and fixtures strategy; (7) knowledge-transfer — post-cycle retrospective covering wins, pain points, and next-cycle changes. Applies a model-first, no-code-dump contract: lead with diagrams and schemas, never include full implementations. Saves reports under __reports__/TOPIC/ using round-versioned naming.

Write GitHub pull request bodies and Discord release announcement messages for software projects that follow a fork-based contribution workflow and publish releases with Discord announcements. Use this skill whenever the user wants to draft, write, or generate: (1) a PR message for a dev-branch contribution from a fork into the upstream repo's dev branch, (2) a PR message merging the upstream dev branch into its main branch for a versioned release, or (3) a Discord announcement for a dev pre-release or a stable release. Also triggers for phrases like "write the PR", "draft the release notes", "Discord announcement for the new version", "PR description for the merge", "write my PR body", or any request involving release communication for a project with this branching model.

Generates and executes a git commit following Conventional Commits format and org narrative conventions. Enforces WHY-focused message writing, explicit-topic scope naming, scope consistency across related commits, and history-aware style matching. Use when the user asks to commit changes, create a commit, or stage and commit work — including slash-command invocation like /commit or /committing-changes. Also applies when the user has completed a feature, fix, or refactor and needs to record it with a semantically meaningful, commitlint-compliant message.