csdlc-craft-agent-prompt

Generate a deterministic Claude Code execution prompt from a refined CSDLC ticket.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-craft-agent-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csdlc-craft-agent-prompt
Source: https://github.com/danhannah94/claymore-plugins/tree/main/csdlc/skills/csdlc-craft-agent-prompt
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-craft-agent-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refined CSDLC tickets often stall at handoff to sub-agents. This skill translates a polished ticket into a precise, executable prompt that a Claude Code sub-agent can run without back-and-forth, bridging refinement and execution.

Core Features & Use Cases

  • Translates a refined ticket into a deterministic, execution-ready prompt for sub-agents.
  • Encapsulates the standard CSDLC prompt structure: Setup, Task context, Acceptance criteria, Boundaries, Verification, and Boilerplate.
  • Use Case: When a ticket reaches ready-for-execution, generate a ready-to-submit Claude Code prompt aligned with project conventions.

Quick Start

Provide a ready-to-run Claude Code prompt for the specified ticket using the standard AGENT_BASE structure.

Frequently Asked Questions about csdlc-craft-agent-prompt

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

FAQPage Schema
How do I generate a prompt for Claude Code from a refined ticket?

Generate a prompt for Claude Code by translating a refined ticket into a deterministic execution structure covering Setup, Task context, Acceptance criteria, Boundaries, Verification, and Boilerplate, eliminating back-and-forth clarification.

What sections should an AI sub-agent prompt include for deterministic execution?

An AI sub-agent prompt should include Setup, Task context, Acceptance criteria, Boundaries, Verification, and Boilerplate sections, alongside references to design docs, to ensure deterministic and safe execution.

How do I stop Claude Code sub-agents from requiring constant clarification during execution?

Stop Claude Code sub-agents from requiring clarification by crafting a precise execution prompt that reads the ticket doc, repo context, and AGENT_BASE guidance to produce a safe, deterministic prompt.

Do I need an AGENT_BASE guidance file to craft sub-agent prompts for ticket automation?

Yes, you need AGENT_BASE guidance to craft sub-agent prompts for ticket automation, as it provides the project conventions needed to produce a deterministic, execution-ready prompt aligned with repo context.

What is the best way to hand off refined software tickets to AI coding agents?

The best way to hand off refined software tickets to AI coding agents is generating a structured execution prompt that encapsulates boundaries and verification criteria, bridging refinement and execution without manual intervention.