Skip to content
cccskills
FreePublished on GitHub

goal-poteto-style-definition

Ask a few focused questions to define a goal, checkable finish conditions, evidence of completion, and constraints. Use when the user wants help clarifying what success means before doing the work.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Goal Poteto Style Definition

Ask the user a few concise questions to clearly define:

  • The goal: What outcome do they want, and why?
  • Checkable finish conditions: What specific, observable conditions must be true for the work to be done?
  • Evidence: What will you show the user to demonstrate that each finish condition and the overall goal have been reached?
  • Constraints: What limits apply, such as scope, time, budget, tools, or things to preserve or avoid?

Use what is already known from the conversation. Ask only about meaningful gaps, in small batches, and follow up where answers are still ambiguous. Suggest concrete finish conditions and evidence when that makes answering easier.

After the answers are clear, summarize the goal, finish conditions, evidence for each condition, and constraints in a short brief. Make any remaining assumptions explicit.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Investigate why a defect or insufficiency was introduced and accepted by tracing code, pull requests, task context, and accessible development sessions. Use for second-order learning after a fix, blameless root-cause analysis, or preventing a recurring class of engineering mistakes.

The English summary is being prepared. Showing the original description.

paperclipai/agent-plugins5Updated Oct 21, 2026

Design, refine, implement, or review application UI and user journeys with minimal controls, clear actions, shared components, realistic prototypes, and polished behavior. Use for product screens, forms, onboarding, navigation, settings, and chat/task interfaces; not backend-only work or general graphic design.

The English summary is being prepared. Showing the original description.

paperclipai/agent-plugins5Updated Oct 21, 2026

Structure any communication artifact — documents, reports, plans, issue comments, PR descriptions, emails, presentations, slides, charts, and dashboards — using Jean-luc Doumont's "Trees, Maps, and Theorems" method. Use whenever the goal is to get a message across to a busy audience, when asked to improve clarity or structure of writing or slides, or when a deliverable will be judged by whether readers act on it, not just read it.

The English summary is being prepared. Showing the original description.

paperclipai/agent-plugins5Updated Oct 21, 2026

See all skills by paperclipai

Report a problem with this skill