From formal-verify
Meta-cognitive decision support that analyzes current context and surfaces intelligent next-step options to the user. Use this skill when: (1) User explicitly invokes /checkpoint, (2) Significant work has been completed and a checkpoint is valuable, (3) Uncertainty or ambiguity exists about requirements or approach, (4) Task complexity has expanded beyond initial scope, (5) Before finalizing or committing to ensure nothing is missed. This skill pauses execution, assesses the situation holistically, and presents 2-5 contextually-appropriate options via AskUserQuestion, with a recommended option and rationale.
npx claudepluginhub petekp/agent-skills --plugin literate-guideThis skill uses the workspace's default tool permissions.
Pause, assess, and surface intelligent next-step options to the user.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Pause, assess, and surface intelligent next-step options to the user.
Suggest this skill (without being asked) when detecting:
Silently evaluate the current state across these dimensions (do not output this analysis):
Based on assessment, generate 2-5 contextually-appropriate options. Draw from (but don't limit to) these archetypes:
| Archetype | When Relevant |
|---|---|
| Commit progress | Meaningful progress made, good stopping point |
| Systems audit | Complex changes, potential for bugs or regressions |
| Prioritize/plan | Multiple pending tasks, unclear what matters most |
| Re-evaluate decisions | Low confidence in recent choices, new information available |
| Clarify with user | Assumptions made, requirements ambiguous |
| Test/verify | Code works but edge cases untested |
| Refactor/clean up | Code functional but messy |
| Document | Complex logic that needs explanation |
| Step back | May be overcomplicating or missing simpler solution |
| Continue current path | Clear next step, no reason to pause |
Option generation principles:
Choose one option as recommended. The recommendation should reflect:
Use AskUserQuestion with this structure:
Question: "What would you like to do next?"
Header: "Next step" (or contextually appropriate 1-2 words)
Options: [generated options with descriptions]
Option format:
label: Action verb phrase (e.g., "Commit current progress", "Run systems audit")description: 1 sentence explaining what this involves and why it might be valuableRecommendation:
For a scenario where a feature was just implemented but with some shortcuts:
AskUserQuestion:
question: "Feature implementation complete. What would you like to do next?"
header: "Next step"
options:
- label: "Review and refactor (Recommended)"
description: "Clean up the shortcuts taken during implementation before they become technical debt. The core logic works but could be more maintainable."
- label: "Add test coverage"
description: "Write tests for the new feature to catch edge cases and prevent regressions."
- label: "Commit and move on"
description: "The feature works - commit it and tackle the next task. Can refactor later if needed."
- label: "Walk me through what was built"
description: "Explain the implementation so you can verify it matches your expectations before proceeding."