Run any Skill in Manus with one click

tools

Stars9

Forks3

UpdatedFebruary 11, 2026 at 05:14

Use when working with specification tooling that automates the spec-driven development workflow — from generating specs to creating plans and tasks from specifications. USE FOR: spec-driven development tooling, spec-to-code automation, specification management tools, choosing spec tools DO NOT USE FOR: writing specifications manually (use documentation sub-skills), creating diagrams (use diagramming sub-skills)

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Tyler-R-Kendrick

Tyler-R-Kendrick/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

21 files

SKILL.md

readonly

name	tools
description	Use when working with specification tooling that automates the spec-driven development workflow — from generating specs to creating plans and tasks from specifications. USE FOR: spec-driven development tooling, spec-to-code automation, specification management tools, choosing spec tools DO NOT USE FOR: writing specifications manually (use documentation sub-skills), creating diagrams (use diagramming sub-skills)
license	MIT
metadata	{"displayName":"Specification Tools","author":"Tyler-R-Kendrick"}
compatibility	claude, copilot, cursor
references	[{"title":"GitHub Spec Kit","url":"https://github.com/github/spec-kit"},{"title":"Spec Kit — Official Documentation","url":"https://speckit.org/"}]

Specification Tools

Overview

Specification tools automate the workflow from written specs to implementation. They bridge the gap between documentation and code by generating plans, tasks, and implementations from structured specifications.

Tool Landscape

Tool	Purpose	Integration
GitHub Spec Kit	Spec-driven development with AI agents	Claude, Copilot, Cursor

Best Practices

Use spec tools to enforce a structured workflow — constitution → specify → clarify → plan → tasks → implement.
Keep generated specs in version control alongside your code.
Treat spec tooling as a development accelerator, not a replacement for architectural thinking.

More from this repository

same repository

improve

Tyler-R-Kendrick/agent-skills

Use when producing agent/LLM evals, synthetic simulation data, or self-improvement pipelines for prompts, code, skills, agents, harnesses, and workflows. Covers AgentEvals/AgentV, Agent Skills evals, ASSERT, GEPA, Trace, VISTA, Agent Lightning, SkillOpt, Simula-style data design, progressive disclosure, deterministic workspaces, and release evidence. USE FOR: eval creation, EVAL.yaml, AgentEvals, AgentV, evals.json, ASSERT, judge-traces, behavior taxonomy, judges, graders, rubrics, synthetic data, simulation data, Simula, QDC, source-grounded generation, prompt optimization, agent improvement, skill improvement, harness hardening, progressive disclosure, deterministic workflows, GEPA, Trace, VISTA, Agent Lightning, SkillOpt DO NOT USE FOR: ordinary unit/integration tests without AI quality criteria (use testing), refactoring without eval or trace feedback (use refactor), generic Agent Skills packaging without eval or improvement work (use agent-skills)

2026-06-099

Tyler-R-Kendrick/agent-skills

Use when working with AI agent protocols, standards, interoperability specifications, evaluation contracts, synthetic simulation data, improvement pipelines, and agent steering workflows. Covers MCP, A2A, ACP, Agent Skills, AGENTS.md, ADL, Improve, x402, AP2, MCP Apps, cagent, and learn. USE FOR: agent protocol selection, comparing MCP vs A2A vs ACP, understanding agent standards ecosystem, choosing payment protocols, choosing eval standards, choosing improvement techniques, choosing synthetic data simulation techniques, steering from user feedback DO NOT USE FOR: specific protocol, eval, or improvement implementation details (use the sub-skills: mcp, a2a, acp, improve, learn, x402, etc.)

2026-06-099

learn

Tyler-R-Kendrick/agent-skills

Use when a user corrects, rejects, edits, or redirects an LLM/agent response and the correction should become a reusable reasoning strategy. Converts feedback into generalized learnings for ~/.agents/STEERING.md with linked RDF/Turtle evidence. USE FOR: user corrections, preference feedback, rejected agent behavior, reasoning strategy updates, steering file maintenance DO NOT USE FOR: storing task facts (use memory), ordinary skill authoring (use agent-skills), project instruction files unrelated to feedback (use agents-md)

2026-06-089

a2a

Tyler-R-Kendrick/agent-skills

Use when implementing the Agent-to-Agent (A2A) protocol for inter-agent communication, task delegation, and multi-agent collaboration. USE FOR: agent-to-agent communication, task delegation between agents, Agent Card publishing, multi-agent collaboration DO NOT USE FOR: tool integration (use mcp), agent payments (use ap2 or x402), agent definition (use adl)

2026-02-119

acp

Tyler-R-Kendrick/agent-skills

Use when implementing the Agent Communication Protocol (ACP) for REST-based agent-to-agent communication, task delegation, and multimodal message exchange. USE FOR: ACP agent servers, ACP client integration, agent discovery via manifests, run lifecycle management, session-based stateful workflows, BeeAI agents DO NOT USE FOR: JSON-RPC agent communication (use a2a), tool integration for LLMs (use mcp), agent payments (use ap2 or x402), agent definition (use adl)

2026-02-119

adl

Tyler-R-Kendrick/agent-skills

Use when defining AI agents declaratively with Agent Definition Language (ADL). Covers agent identity, LLM configuration, tools, permissions, RAG inputs, and governance metadata. USE FOR: declarative agent blueprints, agent identity and permissions, LLM configuration, governance metadata DO NOT USE FOR: agent runtime orchestration (use cagent), tool integration (use mcp), agent communication (use a2a)

2026-02-119

name	tools
description	Use when working with specification tooling that automates the spec-driven development workflow — from generating specs to creating plans and tasks from specifications. USE FOR: spec-driven development tooling, spec-to-code automation, specification management tools, choosing spec tools DO NOT USE FOR: writing specifications manually (use documentation sub-skills), creating diagrams (use diagramming sub-skills)
license	MIT
metadata	{"displayName":"Specification Tools","author":"Tyler-R-Kendrick"}
compatibility	claude, copilot, cursor
references	[{"title":"GitHub Spec Kit","url":"https://github.com/github/spec-kit"},{"title":"Spec Kit — Official Documentation","url":"https://speckit.org/"}]

Specification Tools

Overview

Tool Landscape

Tool	Purpose	Integration
GitHub Spec Kit	Spec-driven development with AI agents	Claude, Copilot, Cursor

Best Practices

Use spec tools to enforce a structured workflow — constitution → specify → clarify → plan → tasks → implement.
Keep generated specs in version control alongside your code.
Treat spec tooling as a development accelerator, not a replacement for architectural thinking.