New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Delegation Prompt Crafter

by alirezarezvani in alirezarezvani/claude-cto-team

Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect).

MITAuto-check passedAgent Workflows

Install Delegation Prompt Crafter

skills CLI
$ npx skills add alirezarezvani/claude-cto-team --skill delegation-prompt-crafter -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-cto-team delegation-prompt-crafter --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/delegation-prompt-crafter .claude/skills/delegation-prompt-crafter && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
delegation-prompt-crafter
GitHub stars
117
Token cost
~2.2k tokens
SKILL.md length
532 words
Files
4
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect).

  • Works in 4 steps: The Information Dump → The Vague Task → The Missing Constraints → …
  • Tasks that involve Subagents
  • SKILL.md covers When to Use, Why This Matters, Delegation Prompt Structure and Agent-Specific Templates, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Delegation Prompt Crafter is an agent skill from alirezarezvani/claude-cto-team. Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect). Use after clarification is complete, before routing to specialist agents. Ensures agents receive complete context for effective work.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `prompt-templates/architect-delegation.md`, `prompt-templates/mentor-delegation.md` and `prompt-templates/ml-architect-delegation.md`).

It sits in Agent Workflows, covering Subagents. The repository describes itself as: Your personal CTO Team for Claude Code . These Subagents will help you challenging yourself while you plan and execute. The licence is MIT.

When your agent uses it

  • Tasks that involve Subagents

Example prompts

  • “/delegation-prompt-crafter”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. The Information Dump
  2. The Vague Task
  3. The Missing Constraints
  4. The Forgotten Handoff

What it can do on your machine

Read from SKILL.md and the folder at commit a5bbb78. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Delegation Prompt Crafter loads about 2.2k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 532 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alirezarezvani/claude-cto-team at commit a5bbb78, republished under its MIT licence (© alirezarezvani). 532 words, ~2,155 tokens.

Download SKILL.mdSave it as .claude/skills/delegation-prompt-crafter/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
delegation-prompt-crafter
description
Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect). Use after clarification is complete, before routing to specialist agents. Ensures agents receive complete context for effective work.

Delegation Prompt Crafter

Creates structured, context-rich prompts for specialist agents that maximize their effectiveness and minimize back-and-forth.

When to Use

  • After clarification-protocol has resolved ambiguities
  • When routing to cto-architect for design work
  • When routing to strategic-cto-mentor for validation
  • When routing to cv-ml-architect for ML-specific architecture
  • For any handoff between agents in a workflow

Why This Matters

Specialist agents work best with:

  1. Clear context: Business goals, constraints, current state
  2. Specific task: Exactly what deliverable is expected
  3. Structured requirements: Must-haves vs nice-to-haves
  4. Quality criteria: How to evaluate success

Without this structure, agents may:

  • Ask redundant questions (wasting time)
  • Solve the wrong problem (misunderstanding context)
  • Over-engineer or under-engineer (missing constraints)
  • Produce outputs in wrong format (unclear expectations)

Delegation Prompt Structure

Every delegation prompt follows this format:

markdown
## CONTEXT

### Business Goal
[What business outcome this serves]

### Current State
[Relevant existing systems, constraints, decisions]

### Key Constraints
- [Constraint 1: e.g., "Budget: < $10K/month infrastructure"]
- [Constraint 2: e.g., "Timeline: MVP in 8 weeks"]
- [Constraint 3: e.g., "Team: 3 senior engineers, Python/React expertise"]

### Background Information
[Any relevant context from clarification or previous agents]

---

## TASK

### Primary Deliverable
[Exactly what output is expected]

### Format Requirements
[Structure, sections, level of detail expected]

### Scope Boundaries
- **In scope**: [What to cover]
- **Out of scope**: [What to explicitly exclude]

---

## REQUIREMENTS

### Must-Haves
- [Critical requirement 1]
- [Critical requirement 2]

### Nice-to-Haves
- [Optional enhancement 1]
- [Optional enhancement 2]

### Quality Criteria
- [Criterion 1: e.g., "Architecture must support 10x growth"]
- [Criterion 2: e.g., "Trade-offs explicitly documented"]

### Integration Points
- [What this output feeds into: e.g., "Will be validated by strategic-cto-mentor"]
- [What depends on this: e.g., "Development team will implement from this"]

---

## ADDITIONAL CONTEXT

[Any other relevant information, links to documentation, previous decisions, etc.]

Agent-Specific Templates

See the prompt-templates folder for pre-built templates:

Crafting Guidelines

Context Section

Business Goal: Be specific about outcomes, not activities

  • Bad: "Build a notification system"
  • Good: "Enable real-time alerts so users act on time-sensitive events, reducing missed opportunities by 50%"

Current State: Include what exists and what's working

  • Existing architecture and tech stack
  • Pain points with current solution
  • Previous attempts and why they failed
  • Existing integrations that must be preserved

Constraints: Be explicit about non-negotiables

  • Budget (infrastructure and development)
  • Timeline (deadlines, milestones)
  • Team (size, skills, availability)
  • Technical (must-use technologies, compliance)
  • Political (stakeholder preferences, past decisions)
Task Section

Primary Deliverable: One clear output

  • Bad: "Help us with the architecture"
  • Good: "Provide a system architecture design document with component diagrams, data flow, and technology recommendations"

Format Requirements: Specify structure

  • "7-section architecture document per standard format"
  • "Executive summary (2 pages max) + detailed appendix"
  • "Focus on Phase 1 MVP, with notes on Phase 2 considerations"

Scope Boundaries: Prevent scope creep

  • Explicitly state what's NOT included
  • Call out decisions already made
  • Identify what other agents will handle
Show full SKILL.md (218 more words)Show less
Requirements Section

Must-Haves vs Nice-to-Haves: Force prioritization

  • Must-haves are blocking—solution fails without them
  • Nice-to-haves are enhancements—can be deferred

Quality Criteria: Measurable success

  • "Latency < 200ms at p95"
  • "Support 100K concurrent users"
  • "Cost < $5K/month at launch scale"

Integration Points: Connect the workflow

  • What happens after this agent finishes?
  • Who consumes this output?
  • What format do downstream consumers need?

Common Mistakes to Avoid

1. The Information Dump

Bad: Copying entire conversation history into delegation Good: Distill to relevant context only

2. The Vague Task

Bad: "Design a good system" Good: "Design a notification system architecture that supports 100K users, uses our existing PostgreSQL database, and costs < $2K/month"

3. The Missing Constraints

Bad: Letting agent assume unlimited budget/time Good: Explicitly stating constraints, even if flexible

4. The Forgotten Handoff

Bad: No mention of what happens next Good: "This design will be validated by strategic-cto-mentor before implementation begins"

Output Examples

Example 1: Architecture Delegation
markdown
## CONTEXT

### Business Goal
Enable customers to receive real-time notifications for order status changes, reducing support tickets about "where's my order" by 60%.

### Current State
- Monolithic Node.js backend, PostgreSQL database
- Notifications currently sent via email batch (hourly)
- 50K active users, expecting 200K in 12 months
- Mobile app (React Native) and web app (React)

### Key Constraints
- Budget: < $3K/month additional infrastructure
- Timeline: MVP in 6 weeks, full rollout in 10 weeks
- Team: 2 backend engineers, 1 mobile engineer
- Must integrate with existing authentication system

### Background Information
User research shows 73% of support tickets are order status questions. Push notifications tested well in user interviews.

---

## TASK

### Primary Deliverable
System architecture design for real-time notification system

### Format Requirements
Standard 7-section architecture document:
1. Executive Summary
2. System Architecture (with diagrams)
3. Technology Stack Justification
4. Implementation Roadmap
5. Risk Assessment
6. Code Examples (WebSocket integration)
7. Deployment Strategy

### Scope Boundaries
- **In scope**: Backend notification service, mobile push integration, delivery tracking
- **Out of scope**: Email notifications (keep existing), SMS notifications (Phase 2)

---

## REQUIREMENTS

### Must-Haves
- Real-time delivery (< 5 second latency)
- Support for 200K users with 20% daily active
- Push notifications on iOS and Android
- Fallback to email if push fails

### Nice-to-Haves
- Notification preferences per user
- Read receipts / delivery confirmation
- Rich notifications with images

### Quality Criteria
- p95 latency < 5 seconds from event to notification
- 99.9% delivery success rate
- Infrastructure cost < $3K/month at 200K users

### Integration Points
- Will be validated by strategic-cto-mentor before implementation
- Development team will implement from this architecture
- Must integrate with existing user service for preferences

---

## ADDITIONAL CONTEXT

Previous attempt at WebSockets failed due to connection management complexity. Team prefers managed solutions where possible. AWS is our cloud provider.

Validation Checklist

Before sending delegation prompt, verify:

  • Business goal is outcome-focused, not activity-focused
  • All critical constraints are explicitly stated
  • Task is specific with clear deliverable
  • Format requirements are defined
  • Scope boundaries prevent scope creep
  • Must-haves are truly must-haves (not nice-to-haves in disguise)
  • Quality criteria are measurable
  • Integration points explain the workflow context
  • No vague terms or buzzwords remain

References

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in skills/delegation-prompt-crafter of alirezarezvani/claude-cto-team.

  • SKILL.md
  • prompt-templates/architect-delegation.md
  • prompt-templates/mentor-delegation.md
  • prompt-templates/ml-architect-delegation.md

Open the folder on GitHubat commit a5bbb78

Compare with similar skills

Delegation Prompt Crafter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Delegation Prompt Crafter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Delegation Prompt Crafter this skillalirezarezvani/claude-cto-team117—~2.2kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25841 repos~1.5kAutomated safety check: PassNone
Reflect on Session Learningscursor/plugins11k5 repos~1.2kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 41 repos~1.5k tokens
    Agent WorkflowsAuto-check passed

  • Reflect on Session Learnings

    cursor/plugins

    Official

    Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.

    11k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Paseo Advisor Second Opinion

    getpaseo/paseo

    Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed

  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~11k tokens
    Agent WorkflowsAuto-check passed

More from alirezarezvani/claude-cto-team

All 12 skills in this repo

  • Antipattern Detector

    alirezarezvani/claude-cto-team

    Detect common technical and organizational anti-patterns in proposals, architectures, and plans.

    117 GitHub stars~2.1k tokensUpdated 9 mo ago
    Auto-check passed

  • Architecture Pattern Selector

    alirezarezvani/claude-cto-team

    Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints.

    117 GitHub stars~1.6k tokensUpdated 9 mo ago
    Auto-check passed

  • Assumption Challenger

    alirezarezvani/claude-cto-team

    Identify and challenge implicit assumptions in plans, proposals, and technical decisions.

    117 GitHub stars~2.4k tokensUpdated 9 mo ago
    Auto-check passed

  • Cost Estimator

    alirezarezvani/claude-cto-team

    Infrastructure and development cost estimation for technical projects.

    117 GitHub stars~3k tokensUpdated 9 mo ago
    Auto-check passed

  • ML Cv Specialist

    alirezarezvani/claude-cto-team

    Deep expertise in ML/CV model selection, training pipelines, and inference architecture.

    117 GitHub stars~3.1k tokensUpdated 9 mo ago
    Auto-check passed

  • Request Analyzer

    alirezarezvani/claude-cto-team

    Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification.

    117 GitHub stars~1.3k tokensUpdated 9 mo ago
    Auto-check passed

Categories

Questions about Delegation Prompt Crafter

What does Delegation Prompt Crafter do?

Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect). Delegation Prompt Crafter is an agent skill from alirezarezvani/claude-cto-team. Transform clarified user requests into structured delegation prompts optimized for specialist agents (cto-architect, strategic-cto-mentor, cv-ml-architect).

When should I use Delegation Prompt Crafter?

Delegation Prompt Crafter fits situations like: tasks that involve Subagents.

How do I install Delegation Prompt Crafter in Claude Code?

Run `npx skills add alirezarezvani/claude-cto-team --skill delegation-prompt-crafter -a claude-code`. Or copy the skill folder (skills/delegation-prompt-crafter in alirezarezvani/claude-cto-team) into .claude/skills/delegation-prompt-crafter in your project. Claude Code loads it when a task matches its description.

How do I install Delegation Prompt Crafter in Codex?

Run `npx skills add alirezarezvani/claude-cto-team --skill delegation-prompt-crafter -a codex`. Or copy the skill folder (skills/delegation-prompt-crafter in alirezarezvani/claude-cto-team) into .agents/skills/delegation-prompt-crafter in your project. Codex loads it when a task matches its description.

Can I use Delegation Prompt Crafter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-cto-team --skill delegation-prompt-crafter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/delegation-prompt-crafter, .gemini/skills/delegation-prompt-crafter, .github/skills/delegation-prompt-crafter and .opencode/skills/delegation-prompt-crafter in your project.

What does Delegation Prompt Crafter need to run?

SKILL.md names no scripts, command-line tools or credentials: Delegation Prompt Crafter is instructions for the agent only. Our summary lists: Node.js.

Does Delegation Prompt Crafter access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Delegation Prompt Crafter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Delegation Prompt Crafter use?

Delegation Prompt Crafter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Delegation Prompt Crafter use?

About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Delegation Prompt Crafter?

Skills that share tags, products or a category with Delegation Prompt Crafter: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Reflect on Session Learnings (cursor/plugins, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Delegation Prompt Crafter?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-cto-team, which has 117 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on December 18, 2025.

Source: alirezarezvani/claude-cto-team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.