daviswhitehead-product-playbook-for-agentic-coding-plugin

Plugin daviswhitehead-product-playbook-for-agentic-coding-plugin from marketplace cascade-ai-ml-agents-misc-1 in joshuarweaver/cascade-ai-ml-agents-misc-1. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• google-tasks

  This skill should be used whenever the user wants to add a to-do, reminder, action item, or task to Google Tasks — e.g. "add a task", "remind me to", "put X on my to-do list", "create a Google Task". It points to the create_google_task MCP tool and explains setup if it is not yet connected.

• image-generation

  Generate images using OpenAI's API. Use this skill when creating logos, illustrations, marketing assets, or any visual content that can be generated from text prompts.

• autonomous-execution

  Patterns for autonomous project execution with minimal human intervention. Use this skill when executing well-defined tasks autonomously, including validation strategies, stop conditions, and quality gates. Don't use when doing a single task interactively with the user, or when the project lacks a t

• chat-insights

  Patterns for analyzing chat sessions to extract product insights. Covers session sampling, evidence validation, idea deduplication, PII handling, data quality assessment, and prompt injection defense. Don't use for capturing a single session's learnings (use learning-capture instead), or for improvi

• codebase-docs-search

  Patterns for finding and using project documentation at runtime. Use this skill when you need to search for existing documentation, solutions, patterns, or learnings in a codebase before starting work. Don't use when you already know the file path, or when searching for code (use Grep/Glob directly)

• conciseness-check

  Quality check for AI-generated output. Detects and removes hedge stacking, throat-clearing, motivational padding, restating, and unnecessary transitions. Use before presenting any substantive artifact to the user. Don't use for code comments or commit messages (those have their own conventions).

• learning-capture

  Multi-trigger, dual-target learning capture patterns. Use this skill to understand how to capture learnings at different points in the development workflow and route them to appropriate targets (codebase docs or plugin improvements). Don't use when saving session state for resumption (use session-ch

• mobile-debugging

  Patterns for debugging mobile-specific issues on iOS Safari and Android Chrome. Use this skill when encountering viewport, keyboard, or touch-related bugs that only reproduce on real mobile devices. Don't use for general debugging (use /playbook:debug instead), or for desktop browser issues.

• session-checkpoint

  Persist working context across sessions and context compaction events. Write checkpoints at session end, read at session start. Prevents re-orientation tax from context amnesia. Don't use when the session is short (fewer than 3 tasks), or for capturing learnings (use learning-capture instead).

• session-start-status

  Produce a 5-bullet session-start orientation summary by reading tasks.md, recent git log, and the latest specstory tail. Run at the start of any session that resumes work on an active project. Don't use when starting a brand-new project from scratch (use /playbook:foundations or /playbook:tech-plan

• stitch-integration

  Shared patterns and best practices for Google Stitch MCP integration. Referenced by all design pipeline commands (design-system, design-spec, mockups, design-critique, design-to-code, design-verify). Don't use when the project doesn't use Stitch for design, or for general UI implementation without m

• user-journey-testing

  Patterns for defining and executing end-to-end user journeys via browser automation at major milestones. Catches integration bugs that component tests miss. Don't use for unit testing, API testing, or debugging a single component. Don't use mid-task — use at milestone boundaries only.

Similar plugins