agent-spec
FeaturedSpecify an autonomous or tool-using AI agent before building it. Use when asked to design an AI agent, define an agent's tools and guardrails, scope what an agent is allowed to do, or write an agent spec/PRD. Produces an agent spec — goal & scope, tools with permissions, the control loop, guardrails & approval gates, memory, escalation/handoff, evaluation, and failure handling.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- mohitagw15856
- Repository
- mohitagw15856/pm-claude-skills
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- HTML
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
specify
Interview the user to produce a complete, agent-ready specification, then emit what is needed to build it: for a coded feature/agent a phase-scoped build prompt, or for a skill / declarative agent the artifact itself (SKILL.md / AGENT.md). Surfaces every assumption for review, slices the work into a phased plan, and runs a build-readiness (model/effort) check. Use when the user wants to design, specify, plan, or scope a new agent, feature, or skill; turn a vague idea, PRD, or plan into a rigorous spec; write requirements in EARS / SHALL with testable acceptance criteria; produce a build prompt for a coding agent; or amend, advance, review, audit or sweep an existing spec under specs/ for drift and staleness. Reasoning-driven, one question at a time.
agent-scoping
Use before building any AI agent or skill, or when the user says "should we build an agent for this", "can AI do this", "automate this workflow", "where should we use AI", "build me an agent". Decides what to build, what to refuse, and what to leave manual. Produces an agent brief with a success threshold and a kill criterion. Writes workspace/agents/<name>/brief.md. Scopes one agent. Not the org-level AI policy, data boundary, or readiness question, which is `ai-governance`.
agent-design
design and review llm agent systems, tool interfaces, and skill boundaries. use when chatgpt needs to decide whether a task should be handled by a prompt, workflow, skill, tool, single-agent loop, or multi-agent system; define tool schemas, instructions, guardrails, evaluation plans, or permission boundaries; or critique an existing agent design for over-orchestration, weak context handling, missing verification, or poor tool design.