prompt

Route user intent to member skills for prompt validation without execution.

6|1|Updated Jan 5, 2026

Search Tags:#workflow #discovery #safety #prompt #orchestrate #exec #forge

Ready to run

npx skills add https://github.com/JordanGunn/skills --skill prompt-jordangunn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prompt
Source: https://github.com/JordanGunn/skills/tree/main/skills/prompt
Command: npx skills add https://github.com/JordanGunn/skills --skill prompt-jordangunn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the discovery and routing of user intent across member skills to form and validate prompts without executing them.

Core Features & Use Cases

Dispatches to member skills in a safe, predictable order to separate intent forging from execution
Ensures a single canonical prompt path and explicit user approval before execution
Provides auditable state transitions and a clean handoff between forge and exec

Quick Start

Provide an initial intent and let the system route it through the prompt-forge and prompt-exec workflow.

Frequently Asked Questions about prompt

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

FAQPage Schema

How do I orchestrate prompt generation without executing the prompt?▼

Prompt orchestration separates intent forging from execution by routing user intent to member skills to form and validate prompts. This enforces a single canonical artifact and explicit user consent before any execution occurs.

What is the safest way to manage prompt state transitions before execution?▼

Managing prompt state transitions safely requires an auditable workflow that separates forging from execution. This approach enforces explicit user approval and provides clean, predictable handoffs between drafting and ready states.

How do I structure a prompt workflow that guarantees explicit user consent?▼

Structuring a prompt workflow for explicit consent requires a single canonical prompt path that separates forge operations from exec operations. This dispatches intent to member skills for validation and provides auditable state transitions before execution.

Why do I need to separate prompt forging from execution in AI workflows?▼

Separating prompt forging from execution provides auditable, safe handoffs by ensuring a single canonical artifact and explicit user consent. This controlled separation validates intent across member skills and prevents unintended actions before execution.

Can I validate user intent across multiple skills before forming a final prompt?▼

Yes, validating user intent across multiple skills involves orchestrating discovery and routing it to member skills. This forms a validated prompt without execution, ensuring explicit user approval and a clean handoff between states.