How do I install the Spec Driven Initiation Engineer skill?

Run npx skillmds@latest add papanito/spec-driven-initiation-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Driven Initiation Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Driven Initiation Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Driven Initiation Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Driven Initiation Engineer?

papanito (@papanito) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Driven Initiation Engineer by papanito

Name: Spec Driven Initiation Engineer
Author: papanito

Spec Driven Initiation Engineer

specialized protocol for spec-driven project initiation using Karpathy's Method — interview for the real goal, decompose into small compartmentalized specs, verify key decisions explicitly, define precise checkable success criteria, and enforce second-AI final verification.

papanito c8d278e 2.9 KB Updated Sep 17, 2026

File contents

spec-driven-initiation-engineer

GOAL

Before any code is written: establish the real goal, small specs, verified decisions, and checkable success criteria — so downstream execution runs without guesswork.

REAL-GOAL INTERVIEW

The user's first statement is the surface task, not the real goal.

"Go to the car wash" (surface) → "Wash my car" (real goal). The real goal changes the solution.
Interview: "What are you actually trying to achieve?" / "If this succeeded perfectly, what would be different?"
Only after the real goal is confirmed does spec authoring begin.

SPEC ANATOMY

Each spec is small enough to read in one sitting:

Real Goal — one sentence: actual outcome.
Scope — what's covered and what's NOT.
Inputs — files, data, context, past examples.
Output — concrete artifact produced.
Verified Decisions — each load-bearing decision marked ✓ verified.
Success Criteria — checkable rules, not vague adjectives.
Format Reference — past example to match, if available.
Dependencies — prior specs consumed (or: none).

PROTOCOLS

Interview: Find the real goal. Bias toward small specs. Verify key decisions. Don't proceed until the real goal is confirmed.
Decompose: Smallest independently-verifiable specs. Each readable in one sitting, independently completable. Sequence by dependency. Never monolithic.
Verify decisions: Every load-bearing decision (scope, format, tools, deps, criteria) explicitly confirmed by user. Mark ✓ verified. Unverified = incomplete = halt.
Success criteria: Checkable rules (not "looks good"). Reference past examples as format spec. Write as done-rule.
Second-AI verification: Separate context checks output against criteria. Producer never self-certifies. Complete only when all pass.

OUTPUT SCHEMA

Real Goal — uncovered outcome.
Specs — each with scope, inputs, output, dependencies.
Verified Decisions — checklist with ✓ verified markers.
Success Criteria — checkable per spec, with format references.
Verification Plan — how second-AI check runs.
Next Action — single step to begin execution.

GUARDRAILS

Interview first, always. No spec without the real-goal interview.
Small is mandatory. Can't read in one sitting? Split.
Verify, don't assume. Silent inference is a bug.
Producer ≠ verifier. Never check own output.
Criteria are checkable. "good"/"complete"/"polished" rejected.
Past examples are authoritative. Reference exists = it IS the format spec.

---name: spec-driven-initiation-engineerdescription: specialized protocol for spec-driven project initiation using Karpathy's Method — interview for the real goal, decompose into small compartmentalized specs, verify key decisions explicitly, define precise checkable success criteria, and enforce second-AI final verification.---# spec-driven-initiation-engineer## GOALBefore any code is written: establish the real goal, small specs, verified decisions, and checkable success criteria — so downstream execution runs without guesswork.## REAL-GOAL INTERVIEWThe user's first statement is the **surface task**, not the real goal.- "Go to the car wash" (surface) → "Wash my car" (real goal). The real goal changes the solution.- Interview: "What are you actually trying to achieve?" / "If this succeeded perfectly, what would be different?"- Only after the real goal is confirmed does spec authoring begin.## SPEC ANATOMYEach spec is small enough to read in one sitting:1. **Real Goal** — one sentence: actual outcome.2. **Scope** — what's covered and what's NOT.3. **Inputs** — files, data, context, past examples.4. **Output** — concrete artifact produced.5. **Verified Decisions** — each load-bearing decision marked `✓ verified`.6. **Success Criteria** — checkable rules, not vague adjectives.7. **Format Reference** — past example to match, if available.8. **Dependencies** — prior specs consumed (or: none).## PROTOCOLS1. **Interview:** Find the real goal. Bias toward small specs. Verify key decisions. Don't proceed until the real goal is confirmed.2. **Decompose:** Smallest independently-verifiable specs. Each readable in one sitting, independently completable. Sequence by dependency. Never monolithic.3. **Verify decisions:** Every load-bearing decision (scope, format, tools, deps, criteria) explicitly confirmed by user. Mark `✓ verified`. Unverified = incomplete = halt.4. **Success criteria:** Checkable rules (not "looks good"). Reference past examples as format spec. Write as done-rule.5. **Second-AI verification:** Separate context checks output against criteria. Producer never self-certifies. Complete only when all pass.## OUTPUT SCHEMA1. **Real Goal** — uncovered outcome.2. **Specs** — each with scope, inputs, output, dependencies.3. **Verified Decisions** — checklist with `✓ verified` markers.4. **Success Criteria** — checkable per spec, with format references.5. **Verification Plan** — how second-AI check runs.6. **Next Action** — single step to begin execution.## GUARDRAILS- **Interview first, always.** No spec without the real-goal interview.- **Small is mandatory.** Can't read in one sitting? Split.- **Verify, don't assume.** Silent inference is a bug.- **Producer ≠ verifier.** Never check own output.- **Criteria are checkable.** "good"/"complete"/"polished" rejected.- **Past examples are authoritative.** Reference exists = it IS the format spec.

Frequently asked questions