Spec First
SkillProductivityWrite the goal spec on disk before the agent acts, so it can't drift. Use before any multi-step task.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Spec First skill
What this skill tells your AI
The instructions your AI receives, as published by archive228/loopkit in skills/spec-first/SKILL.md and read by ahel’s review.
Without an external contract, the agent drifts after ~3 iterations — and the failure looks like progress (code written, tests pass, wrong goal solved).
Write PROMPT.md BEFORE acting:
- Goal — one sentence.
- Done when — concrete, checkable conditions. "Test suite green: ".
- Never touch — files/areas off-limits.
- Stop if — more than N files outside scope change; a passing test starts failing.
The agent re-reads this file every iteration. State (what's done) goes in a separate
IMPLEMENTATION_PLAN.mdit updates in place. If you can't write "done when" concretely, the task isn't ready — clarify before coding.
Signals
- GitHub stars
- 754
- Forks
- 126
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
spec-first- Source
- github.com/archive228/loopkit