ikonushok

Agent Pack Designer — AI skill for Claude Code

AI community

Design minimal AI agent packs for Codex and Claude from project descriptions.

How to install Agent Pack Designer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ikonushok/agent-pack-designer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agent Pack Designer does

Design minimal AI agent packs for Codex and Claude from project descriptions.

Alternatives in AI

  • Repomix — 📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file 22.7k ★
  • AI Research SKILLs — Visual Skills Pack for Obsidian: generate Canvas, Excalidraw, and Mermaid diagrams from text with Claude Code 5.7k ★
  • ML Training Pack — Machine learning model training skills 1.6k ★

README

agent-pack-designer

Design minimal sufficient, validation-driven AI agent packs for Codex and Claude Code from project descriptions, README files, technical specs, or existing repository evidence.

`agent-pack-designer` is a portable Codex skill for creating or auditing project-specific agent packs that are intentionally scoped to the repository's real workflows, risks, and validation evidence. It designs the smallest role set that can handle the work responsibly: context routing, primary workflow ownership, risk or domain review, validation review, and optional trigger-only roles such as architecture, red-team, security, data quality, or release review when the project evidence justifies them.

It focuses on context economy, role separation, reviewer ownership, validation levels, and evidence boundaries, while avoiding speculative agents that add maintenance cost without improving reliability.

The skill also separates optional agent roles from optional project deliverables. Bonus, extra-credit, stretch, and checklist-only sections should not force a new agent, but they must remain visible in the generated workflow or reviewer output with an explicit status such as `implemented`, `not implemented`, `not claimed`, or `blocked`.

Specification discovery covers Spec Kit (`.specify/memory/constitution.md`, `specs/*/spec.md`) and ordinary specs under `spec/`, `specs/`, `docs/spec*`, `docs/requirements*`, `docs/design*`, or README sections. Missing, partial, or placeholder-only structured specs lead to relevant documentation fallback. The skill extracts deliverables, acceptance criteria, non-goals, constraints, and validation expectations with source references; claims above L2 require implementation checks and the evidence for the claimed level. See [Specification Discovery](agent-pack-designer/references/spec-discovery.md).

Contents

New to agent packs or not comfortable with terminal setup? Start with [For Non-Technical Users](#for-non-technical-users).

  • [How