plannotator-setup-goal

Build a structured goal package from a user idea or objective.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Rayzerrek/dotfiles --skill plannotator-setup-goal-rayzerrek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plannotator-setup-goal
Source: https://github.com/Rayzerrek/dotfiles/tree/main/.pi/agent/skills/plannotator-setup-goal
Command: npx skills add https://github.com/Rayzerrek/dotfiles --skill plannotator-setup-goal-rayzerrek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a vague idea or objective into a structured goal package, so planning starts with aligned scope instead of scattered chat.

Core Features & Use Cases

  • User Interviewing: Builds a compact question bundle that captures the facts needed to define the goal well.
  • Fact Sheet Review: Converts interview results into a reviewable list of concrete facts, with automated verification choices.
  • Codebase-Aware Planning: Explores the repository to shape an execution plan that matches the actual implementation surface.
  • Use Case: A user wants to add a feature but only has a rough idea; this Skill helps clarify the goal, capture agreed facts, and produce a ready-to-run plan for /goal.

Quick Start

Ask the assistant to use this Skill to turn your idea into a goal package for /goal.

Frequently Asked Questions about plannotator-setup-goal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague software idea into a structured execution plan?

Interview-driven discovery builds a compact question bundle that captures the facts needed to define the goal well, ensuring your planning starts with aligned scope instead of scattered chat.

What is the best way to plan software changes based on actual codebase implementation?

Fact sheet review converts interview results into a reviewable list of concrete facts with automated verification choices, ensuring all planning decisions are grounded in verified project context.

How do I start goal setup for a new feature when I only have a rough idea?

After completing the interview and fact sheet review, this Skill produces a ready-to-run goal package that you can pass directly to /goal to execute the ordered steps for your software changes.

Can I control the scope of a goal package before generating an execution plan?

Scope control is maintained by requiring persistent goal artifacts and grounding the ordered execution plan in verified project context, preventing the plan from expanding beyond the agreed implementation surface.

Why does my feature planning result in scattered chat instead of an actionable plan?

Unlike scattered chat, this approach enforces persistent goal artifacts and scope control, converting raw ideas into an ordered execution plan that is strictly grounded in verified project context.