agentic-designer-skill

Generate agentic design artifacts for orchestration, memory, tools, and prompts.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Galharel/my-codex-skills --skill agentic-designer-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-designer-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/agentic-designer-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill agentic-designer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design teams often struggle to orchestrate agentic systems, define memory and retrieval strategies, formalize tool contracts, and plan prompt strategies in a coherent, maintainable way. This skill provides a structured approach to produce end-to-end agentic design artifacts.

Core Features & Use Cases

  • Orchestration: define agents, sequencing, parallelism, retries, and escalation paths.
  • Memory/Context/RAG: memory layers, retrieval strategies, and storage boundaries.
  • Tools/MCP: establish tool contracts, capability definitions, and MCP server outline when needed.
  • Prompt strategy: system prompts, role separation, guardrails.
  • Output artifacts: produces docs/agentic.design.packet.json and docs/agentic.design.md for implementation.

Quick Start

Provide the architecture artifacts (docs/architecture.packet.json) and any handoff docs (docs/architecture.handoff.agentic.md) to begin the agentic design process.

Frequently Asked Questions about agentic-designer-skill

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

FAQPage Schema
How do I design end-to-end agentic systems for orchestration and memory?

Designing agentic systems requires structuring orchestration, memory/RAG, tool contracts, and prompt strategy. This skill generates design artifacts specifying agent sequencing, retrieval boundaries, and guardrails for implementation teams.

What is the best way to formalize tool contracts and MCP server outlines?

Formalizing tool contracts involves establishing capability definitions and MCP server outlines. This skill structures tool interfaces and capability definitions to align with backend interfaces and data constraints.

How do I plan RAG memory layers and retrieval strategies for agent workflows?

Planning RAG memory layers involves defining memory storage boundaries and retrieval strategies. This skill provides a structured approach to map out memory layers, retrieval strategies, and context storage boundaries for agent-based workflows.

Do I need architecture artifacts before starting agentic design?

Yes, you need architecture artifacts before starting agentic design. Provide architecture packet JSON files and any handoff docs to begin the process of defining agents, prompt strategy, and orchestration paths.

What output artifacts are generated for agentic system implementation?

The output artifacts generated are a design packet JSON file and a design markdown file. These artifacts document decision logging, orchestration, memory layers, and tool contracts for engineering teams.

Can I define retry and escalation paths for agent orchestration?

Yes, you can define retry and escalation paths for agent orchestration. This skill enables you to specify agents, sequencing, parallelism, retries, and escalation paths within your agentic system design.