持續整合/部署

Use to facilitate cross-functional journey mapping with data-backed insights.

Operational template for building social content calendars with approvals and publishing workflows.

Use when planning multi-channel editorial calendars, enforcing publishing cadences, and coordinating distribution workflows across GTM teams.

Updates the Monarch Initiative publications page with latest data from Google Scholar. Use this when the user asks to update publications, refresh citation metrics, or add new papers to the publications page.

Use when enforcing brand tone, style, and localization rules across copy.

Processes and guardrails for recruiting, scheduling, consent, and incentive fulfillment.

Reporting framework for monitoring trust, sentiment, and regulator-facing KPIs.

Use to package concise executive updates, decks, and decision logs for enterprise pursuits.

Use to structure pricing/packaging proposals with clear fences and value pillars.

Use to craft concise revenue updates for executives and boards.

Use to plan rollout communications, trainings, and assets after pricing changes.

Use to define KPIs, alert thresholds, and reporting cadences for social calendars.

Reporting template for tracking sentiment, risks, and advocacy signals across social + community channels.

Use when producing research-heavy whitepapers or technical guides that require structured argumentation and data.

Prioritizes tests based on ROI and critical user journeys. Use when: deciding test coverage, selecting test types, or budgeting effort.

Renames a Terraform attribute safely without changing its schema or producing an unnecessary diff, while enabling users to use both the previous and subsequent attribute names for a deprecation period.

Explicit-only: pick the next `bd ready` bead via risk-first heuristics; verify dependency/readiness, add missing deps, then mark in progress and comment.

Unified shipping + TRACE self-review protocol (beads, proof, PR). Explicit-only.

Finish the in-progress bead; validate via $close-the-loop; open a PR (do not merge). Explicit-only.

Turn the idea for a feature into a fully-formed PRD/design/specification and implementation-plan. Use when you have a spec or requirements that needs implementation. Use in pre-implementation (idea-to-design) stages to make sure you understand the spec/requirements and ensure you have a correct implementation plan before writing actual code.