Loading...
Loading...
Found 22 Skills
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "ask me questions".
Rates responses and plans against quality rubrics. Used for plan validation, response quality audits, and multi-agent consensus.
Validates optimization plan via parallel multi-agent review (Codex + Gemini) before execution. GO/NO-GO verdict.
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
Cursor PMでアイデアを検証し、Plans.mdを更新してバトンタッチ。2-Agentワークフロー対応。
Continuously question users about their plan or design. Suitable for scenarios where users want to stress-test their plan before building, or when using any "grill" trigger phrases.
Build and inspect dependency-aware DAGs from Cursor-style `.plan.md` files that use `name`, `overview`, `todos`, and `isProject`. Use when you need to turn plan files into launch lanes, validate plan structure, reuse or create saved graph state for an exact plan selection, or feed plan-derived work into `subagent-graph` and `helm`.
Validate implementation plans against DRY, YAGNI, TDD principles and best practices. Use when reviewing plans from pocket-planning or another planning workflow to identify gaps, anti-patterns, and improvement opportunities before execution.
Check a development plan on the issue tracker. Use when the user asks to check or review a plan, or when another skill needs a plan checked before it runs.
Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.