planner-identity

Enforces planning-only roles and validates prompt files for Finesse.

4|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/jonathanung/finesse --skill planner-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-identity
Source: https://github.com/jonathanung/finesse/tree/main/plugins/finesse/skills/planner-identity
Command: npx skills add https://github.com/jonathanung/finesse --skill planner-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces non-negotiable rules and identity constraints for all Finesse planning commands, ensuring consistent and safe AI behavior during task planning.

Core Features & Use Cases

  • Enforces Planning-Only Role: Prevents the AI from executing code or making direct changes to the codebase.
  • Mandates Codebase Exploration: Ensures the AI analyzes the codebase before designing solutions.
  • Strict Phase Adherence: Guarantees all planning phases are followed in order.
  • Use Case: When using Finesse to plan a new feature, this Skill ensures the AI focuses solely on generating a validated prompt and never attempts to write code itself, preventing unintended modifications.

Quick Start

Use the planner-identity skill to ensure all Finesse planning adheres to strict safety and role guidelines.

Frequently Asked Questions about planner-identity

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

FAQPage Schema
How do I prevent an AI agent from executing code or modifying the codebase during task planning?

To enforce a planning-only role for an AI agent, apply strict identity constraints and safety guardrails. This ensures the agent focuses solely on generating validated prompt files and never attempts unauthorized code execution or data exfiltration.

What are AI agent safety guardrails for task planning and how do they work?

AI agent safety guardrails for task planning work by enforcing a strict planning-only identity, mandating codebase exploration before solution design, and validating all outputs as prompt files to prevent unauthorized modifications.

How do I mandate codebase exploration before an AI agent designs a solution?

Mandate codebase exploration by configuring the agent's core identity to enforce strict adherence to predefined planning phases. This guarantees the AI analyzes the existing codebase before designing any solutions.

Can I use an AI agent to generate planning prompts without allowing direct code changes?

Yes, you can restrict an AI agent to generate planning prompts without allowing direct code changes by enforcing a planning-only identity. This prevents unauthorized code execution and ensures all outputs are validated prompt files.

Why does my AI agent skip planning phases or execute code prematurely?

An AI agent skips planning phases or executes code prematurely when it lacks strict identity constraints and operational rules. Enforcing predefined planning phases and a planning-only role ensures consistent, safe behavior during task planning.

What are the limitations of using a planning-only AI agent for software engineering tasks?

The main limitation of a planning-only AI agent is that it cannot execute code or make direct changes to the codebase. Its strict operational rules restrict all outputs to validated prompt files, preventing any actual implementation.