plannotator-setup-goal

Convert a user idea into a /goal package with interview and plan files.

1|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/luan/agents --skill plannotator-setup-goal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plannotator-setup-goal
Source: https://github.com/luan/agents/tree/main/skills/plannotator-setup-goal
Command: npx skills add https://github.com/luan/agents --skill plannotator-setup-goal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It turns an idea or objective into a structured goal package for /goal by gathering user intent, deriving testable facts, and producing an implementation plan grounded in codebase exploration.

Core Features & Use Cases

  • Guided goal setup workflow: Rearticulates the objective, then runs a user-driven Plannotator interview to collect the facts the goal must produce.
  • Fact specification with verification intent: Creates a facts review bundle and records automated verification selections, then writes accepted facts into a human-readable facts.md.
  • Plan grounded in codebase exploration: Produces an ordered plan that identifies files/systems involved, risks, unknowns, and concrete verification steps for each phase.
  • Goal output for execution: Writes a final goal.md that links facts.md and plan.md and provides a clear done condition and next command to launch the goal.

Quick Start

Use plannotator-setup-goal to turn your idea into a goal package by guiding an interview and generating goals/<slug>/goal.md, ready to launch with /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 feature idea into an executable goal package with verifiable success criteria?

To turn a feature idea into an executable goal package, this Skill runs a structured interview to collect intent, derives testable facts, and drafts a codebase-informed execution plan. It outputs a structured goal package ready for automated verification and execution.

What is requirements decomposition for product delivery and when do I need structured interviews?

Requirements decomposition breaks down a broad objective into scoped implementation steps and testable facts. You need structured interviews for this when a feature's scope, success criteria, and constraints must be clarified and grounded in repository evidence before execution.

How to generate an implementation plan grounded in codebase exploration for a new feature?

You can generate an implementation plan grounded in codebase exploration by analyzing the repository to identify involved files and systems. This process produces an ordered plan documenting risks, unknowns, and concrete verification steps for each phase.

Can I automate fact specification and verification intent for product delivery workflows?

Yes, you can automate fact specification by creating a facts review bundle that records automated verification selections. Accepted facts are then written into a human-readable facts.md file to establish verification intent for the goal package.

Does goal planning work without manually reviewing repository evidence for blockers?

Goal planning using this workflow relies on codebase exploration to identify risks, unknowns, and documented blockers automatically. It grounds the execution plan in repository evidence, ensuring the final goal.md contains a clear done condition without manual evidence gathering.

What files does the plannotator-setup-goal workflow generate for launching a goal?

The plannotator-setup-goal workflow generates interview.json, facts-review.json, plan.md, and a final goal.md. These files link the testable facts and implementation plan together, providing a clear done condition and next command to launch the goal.