Agency-Agents Deliverable Templates: How Knowledge Workers Structure Final Outputs

Agency-Agents deliverable templates are Markdown skeletons embedded in each agent's definition file that standardize final outputs into structured, domain-specific reports.

The msitarzewski/agency-agents repository implements a unique approach to AI agent outputs where every knowledge worker produces standardized deliverable templates. These templates ensure consistent, professional hand-offs regardless of whether the agent handles workflow optimization, strategic portfolio management, or developer experience audits.

What Are Agency-Agents Deliverable Templates?

Each agent in the repository functions as a self-contained knowledge worker that concludes its task by emitting a Deliverable Template. These templates are not external documents but Markdown skeletons defined within the agent's own .md definition file.

The templates serve as fill-in-the-blank frameworks that agents populate when completing assignments. This design guarantees that every final output maintains the same predictable structure, making downstream consumption—whether by human reviewers, automated pipelines, or other agents—trivial to process.

Template Location and Structure

Deliverable templates reside in the "📋 Your Deliverable Template" section of each agent's markdown definition file. These files are located throughout the repository root, organized by domain:

• testing/testing-workflow-optimizer.md
• project-management/project-management-studio-producer.md
• specialized/specialized-developer-advocate.md
• marketing/marketing-zhihu-strategist.md
• engineering/engineering-frontend-developer.md

The Standard Template Anatomy

Every agent definition follows a consistent structure that culminates in the deliverable template:

1. Agent definition – YAML header defining name, description, and color
2. Persona & mission – Narrative describing identity, memory, and core rules
3. Technical Deliverables – Bulleted list of concrete items to produce
4. 📋 Your Deliverable Template – Fenced code block containing the Markdown outline
5. Workflow process – Step-by-step instructions driving the agent toward template completion

How Deliverable Templates Work in Practice

When an agent runs, it follows its defined workflow, gathers domain-specific data, and finally writes a document matching its template. This markdown-first approach means agents output structured text that renders immediately as professional reports, plans, or technical artifacts.

From Markdown Skeleton to Completed Output

The template acts as a contract. For example, the Workflow Optimizer agent in testing/testing-workflow-optimizer.md uses this skeleton:

# [Process Name] Workflow Optimization Report

## 📈 Optimization Impact Summary

**Cycle Time Improvement**: [X% reduction with quantified time savings]
**Cost Savings**: [Annual cost reduction with ROI calculation]
**Quality Enhancement**: [Error rate reduction and quality metrics improvement]

## 🔍 Current State Analysis

**Process Mapping**: [Detailed workflow visualization with bottleneck identification]
**Performance Metrics**: [Baseline measurements for time, cost, quality]

## 🎯 Optimized Future State

**Redesigned Workflow**: [Streamlined process with automation opportunities]
**Performance Projections**: [Expected improvements with confidence intervals]

## 🚀 Implementation Roadmap

**Phase 1 – Quick Wins**: [Immediate actions with 30‑day timeline]
**Phase 2 – Medium‑Term**: [Structural changes with 90‑day timeline]
**Phase 3 – Strategic**: [Long‑term transformation initiatives]

## 💰 Business Case & ROI

**Investment Required**: [Total cost of implementation]
**Expected Returns**: [Quantified benefits and payback period]

When the agent completes its analysis, it replaces the bracketed placeholders with actual data, producing a finalized report.

Domain-Specific Deliverable Template Examples

The repository contains specialized templates tailored to distinct professional domains. Each template optimizes for the specific artifacts required in that field.

Workflow Optimization Reports

The Workflow Optimizer agent in testing/testing-workflow-optimizer.md produces comprehensive process improvement documentation. Its deliverable template includes sections for Optimization Impact Summary, Current State Analysis, and Implementation Roadmap, ensuring that workflow audits result in actionable business cases with quantified ROI.

Strategic Portfolio Reviews

The Studio Producer agent defined in project-management/project-management-studio-producer.md generates high-level strategic documents. Its template structures outputs as Strategic Portfolio Reviews containing executive summaries, portfolio metrics, and next-period priorities—designed for leadership consumption and quarterly planning cycles.

Developer Experience Audits

The Developer Advocate agent in specialized/specialized-developer-advocate.md focuses on technical onboarding optimization. Its deliverable template produces DX Audit: Time‑to‑First‑Success Reports that include methodology sections, onboarding flow analysis, and prioritized fix recommendations—critical for improving developer adoption metrics.

API Test Results

The API Tester agent in testing/testing-api-tester.md generates technical testing documentation. Its template structures API Test Results Reports with test matrices, observed behaviors, defect logs, and remediation recommendations—providing engineering teams with structured QA hand-offs.

Marketing Content Strategies

The Zhihu Strategist agent in marketing/marketing-zhihu-strategist.md produces multi-part content marketing deliverables. Unlike single-document agents, this template generates Strategic & Content Documents including Topic Authority Maps, Answer Template Libraries, and Lead-Generation Funnels—enabling comprehensive social media strategy execution.

Frontend Feature Delivery

The Frontend Developer agent in engineering/engineering-frontend-developer.md outputs implementation-ready checklists. Its Frontend Feature Delivery Checklist template includes feature specifications, UI mockup references, component breakdowns, test plans, and deployment steps—ensuring consistent shipping standards for web development tasks.

Common Structural Patterns Across All Templates

Despite domain differences, all Agency-Agents deliverable templates share a common structural DNA. This consistency enables automated parsing and cross-functional collaboration.

The universal scaffold follows this pattern:

# [Title]: [Specific Name]

## 📈 Impact Summary

- **Key metric 1**: …
- **Key metric 2**: …

## 🔍 Current State Analysis

- **Process Mapping**: …
- **Performance Metrics**: …
- **Pain Point Analysis**: …

## 🎯 Optimized Future State

- **Redesigned Workflow / Architecture**: …
- **Performance Projections**: …
- **Technology Integration**: …

## 🚀 Implementation Roadmap

- **Phase 1 – Quick Wins**: …
- **Phase 2 – Medium‑Term**: …
- **Phase 3 – Strategic**: …

## 💰 Business Case & ROI

- **Investment Required**: …
- **Expected Returns**: …
- **Payback Period**: …

---
**Agent Name**: [Your name]  
**Date**: [Date]  
**Signature**: …

Agents swap sections to match their niche—substituting "Answer Template Library" for marketing strategists or "DX Audit" for developer advocates—while maintaining the predictable markdown structure that defines Agency-Agents deliverable templates.

Summary

• Agency-Agents deliverable templates are Markdown skeletons embedded directly in each agent's definition file under the "📋 Your Deliverable Template" section.
• Every agent in the msitarzewski/agency-agents repository—from Workflow Optimizers to Frontend Developers—outputs structured reports that follow domain-specific but structurally consistent templates.
• Templates include standardized sections like Impact Summary, Current State Analysis, Implementation Roadmap, and Business Case, ensuring predictable hand-offs for automated pipelines or human review.
• Source files such as testing/testing-workflow-optimizer.md, project-management/project-management-studio-producer.md, and specialized/specialized-developer-advocate.md demonstrate how these deliverable templates are defined and executed.

Frequently Asked Questions

Where are deliverable templates defined in the Agency-Agents repository?

Deliverable templates are defined within each agent's markdown definition file (.md files) under the repository root. Specifically, each file contains a section titled "📋 Your Deliverable Template" that houses the Markdown skeleton. For example, the Workflow Optimizer defines its template in testing/testing-workflow-optimizer.md, while the Studio Producer uses project-management/project-management-studio-producer.md.

What format do Agency-Agents deliverable templates use?

All deliverable templates use Markdown format enclosed in fenced code blocks within the agent definition files. These templates employ ATX-style headings, bullet lists, and placeholder brackets (e.g., [Process Name], [X% reduction]) that the agent replaces with actual data upon task completion. This markdown-first approach ensures outputs render immediately as professional documents without additional formatting steps.

How do agents populate their deliverable templates?

Agents populate templates by following their defined workflow process—a step-by-step instruction set that guides data gathering and analysis. As the agent collects information (e.g., process metrics, API test results, or portfolio data), it fills in the bracketed placeholders within the template sections. When the workflow completes, the agent outputs the fully populated Markdown document as its final artifact, ensuring every deliverable follows the predefined structure established in the "📋 Your Deliverable Template" section.

Can deliverable templates be customized for specific domains?

Yes, deliverable templates are purpose-built for each agent's domain while maintaining structural consistency. For example, the Developer Advocate in specialized/specialized-developer-advocate.md uses a DX audit template with technical sections like "Time-to-First-Success," while the Zhihu Strategist in marketing/marketing-zhihu-strategist.md employs content strategy templates with "Topic Authority Maps." Despite domain differences, all templates share common structural DNA—Impact Summaries, Current State Analysis, and Implementation Roadmaps—enabling cross-functional compatibility while allowing domain-specific customization.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}