plan-first

Plan and validate user intents before executing actions.

2|1|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/inernoro/prd_agent --skill plan-first
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-first
Source: https://github.com/inernoro/prd_agent/tree/main/.claude/skills/plan-first
Command: npx skills add https://github.com/inernoro/prd_agent --skill plan-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-first ensures that for any task, the user receives a concise, structured analysis before taking action, preventing premature changes and unreviewed executions.

Core Features & Use Cases

  • Concise, structured analysis delivered before execution.
  • Explicit waiting for user confirmation before touching files, writing code, or taking actions.
  • Safe, auditable decision points suitable for software projects, documentation workflows, and research tasks.

Quick Start

Ask me to plan before proceeding, and I will provide a concise plan and wait for your approval.

Frequently Asked Questions about plan-first

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

FAQPage Schema
What is a plan-first workflow and when do I need it for code changes?▼

A plan-first workflow provides a concise, structured analysis before executing any actions. You need it for code changes, file edits, or automated workflows where risk mitigation and explicit approval are essential to prevent unreviewed executions.

How do I enforce explicit approval before an automated workflow modifies files?▼

You enforce explicit approval by using a workflow that requires user confirmation to proceed, advancing only after explicit consent. This creates safe, auditable decision points before touching files, writing code, or taking actions.

Can I use structured analysis to prevent premature changes in software projects?▼

Yes, structured analysis prevents premature changes by delivering a concise plan before execution. It enforces a strict 3-part response pattern and waits for user confirmation, ensuring safe, auditable decision points suitable for software projects.

Is waiting for user confirmation suitable for research tasks and documentation workflows?▼

Waiting for user confirmation is suitable for research tasks and documentation workflows because it enforces a strict 3-part response pattern and requires user confirmation to proceed. This ensures safe, auditable decision points before any changes are made.

Does the plan-first approach stop execution if no explicit consent is given?▼

Yes, the plan-first approach stops execution if no explicit consent is given. It requires user confirmation to proceed and advances only after explicit consent, ensuring no premature changes or unreviewed executions occur.