Ke Spec — Testing skill for Claude Code
Create or refine a requirements-first engineering specification without editing application code.
How to install Ke Spec
Installs to ~/.claude/skills/haithemmihoubi-kiro-engineering-skill-ke-spec/SKILL.md
mkdir -p ~/.claude/skills/haithemmihoubi-kiro-engineering-skill-ke-spec && curl -fsSL https://raw.githubusercontent.com/haithemmihoubi/Kiro-Engineering-Skill/HEAD/commands/ke-spec.md -o ~/.claude/skills/haithemmihoubi-kiro-engineering-skill-ke-spec/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Ke Spec does
description: Create or refine a requirements-first engineering specification without editing application code. argument-hint: [feature-or-bug-summary]
Use the `kiro-engineering` skill in specification mode. Inspect repository instructions and current changes first. Create or update `.specs//requirements.md`, `design.md`, `tasks.md`, `verification.md`, and `decisions.md` as appropriate. Separate facts, assumptions, decisions, unknowns, and out-of-scope behavior. Ask only the
Alternatives in Testing
- Debug — You are tasked with helping debug issues during manual testing or implementation 10k ★
- Flow Spec — NLSpec authoring — use when you need a structured specification from multi-AI research and consensus 2.8k ★
- Add Plugin — Integrate a spec-driven/skill framework as a bundled agtx plugin 1.5k ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Gsd 2 Next
A powerful meta-prompting, context engineering and spec-driven development system that enables agents to work
Refine Requirements
Deprecated v0.2 alias — use /start-app --spec instead. Will be removed in the next major release.
Spec Requirements
Refine proposal.md and capability deltas for an active change. Interviews the user, writes the initial draft t
Rpi Plan
RPI Step 3 — Generate comprehensive planning documentation for a feature that received a GO. Produces pm.md (p
Spec Writer
Specification writer that turns vague intent into precise, buildable specs with acceptance criteria and GitHub
Spec Specify
Phase 1 — Creates the detailed technical specification of a feature: functional requirements, non-functional r
Related Agents
Requirements Architect
Analyze ambiguous feature or bug requests and produce traceable requirements, acceptance criteria, invariants,
QA Requirements Risk Analyst
Analyzes requirements, ambiguity, risk, lifecycle impact, acceptance criteria, and traceability gaps without e
Behavior Tester
Behavior-first tester (فاحص السلوك) — runs an application or code deliverable against an agreed behavior speci