dispatched-prompt-authoring

Write self-contained system prompts and templates for dispatched agent sessions.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill dispatched-prompt-authoring-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatched-prompt-authoring
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/dispatched-prompt-authoring
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill dispatched-prompt-authoring-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dispatched agent sessions cannot ask follow-up questions, so an incomplete or ambiguous prompt causes them to fail, leak their full transcript upward, or act outside their intended scope. This Skill guides the authoring of prompts that are complete, literal instruction sets a session can execute autonomously. ## Core Features & Use Cases - Self-contained prompt construction: Ensures every rule, input, job definition, and output shape is stated directly in the rendered prompt. - Explicit substitution slots: Requires naming every placeholder token and what it resolves to, so no rendered prompt ships with unfilled variables. - Return-value contracts: Defines the exact shape of what the session sends back, typically a single status line, keeping working context inside the session. - Use Case: When building a pipeline that dispatches parallel implementation agents, use this Skill to author each agent's prompt with explicit file paths to read, hard boundaries on what it may write or execute, and a compact return contract. ## Quick Start Author a dispatched-session prompt for an implementation agent that reads its task files itself, states its write boundaries, and returns only a single status line.

Frequently Asked Questions about dispatched-prompt-authoring

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

FAQPage Schema
How do I write a prompt for an autonomous agent session?

Make the rendered prompt the complete, literal instruction set: state the session's inputs, its single job, and its output shape directly in the text. A dispatched session cannot ask follow-up questions, so anything left implicit will be guessed or missed.

How to handle template placeholders in agent prompts?

Name every substitution slot explicitly and state what each token resolves to before dispatch. A rendered prompt that still carries an unsubstituted placeholder is a defect, not a minor detail.

Should I pass file contents inline in an agent prompt?

No. Point the session at the file paths it must open and let it read them itself. Passing large content inline bloats the prompt and couples it to a snapshot that goes stale.

How do I stop a dispatched agent from returning its whole transcript?

Specify the return-value contract precisely, often a single status line, so only that compact result crosses back to the caller. Under-specifying the return is what lets a session leak its entire working context upward.

What boundaries should an agent prompt define?

State what the session writes, what it must not touch, and what it must never execute as explicit obligations in the prompt. A session left to infer its own scope guesses wrong often enough to matter.