dev-kickoff-edho-ferdian

Kickoff and execute development projects from specification documents through a seven-stage loop.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill dev-kickoff-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-kickoff-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/dev-kickoff-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill dev-kickoff-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a development project from scattered planning documents (PRDs, SRS, WBS, RFCs, ADRs) often leads to missed requirements, silent cross-document conflicts, and lost context when sessions end. This Skill turns any set of specification documents into a validated, executable project plan and then builds it task by task with persistent memory. ## Core Features & Use Cases - Document-agnostic intake and validation: Classifies any planning documents into six roles (PRODUCT_INTENT, BEHAVIOR_SPEC, ARCHITECTURE, UX_SPEC, WORK_PLAN, OPS_CONSTRAINTS), cross-checks them on at least four consistency axes, and surfaces BLOCKERs before any code is written. - Project Decision Register and Context Pack: Extracts every binding decision with a traceable source, then generates CLAUDE.md, AGENTS.md, .cursorrules, or copilot-instructions.md plus a project-fit agent roster so any AI tool can pick up the project cold. - Seven-stage execution loop with memory: Runs each task through PLAN, TEST, IMPLEMENT, REVIEW, VERIFY, REMEMBER, IMPROVE, auto-invoking specialist sibling skills, and maintains /project-memory/ files plus Session Snapshots for lossless resume. - Use Case: You have a PRD, an SRS, and a WBS for a new SaaS app. Hand them over, get a validated decision register and context pack, then watch the project get built task by task with test-first discipline and resumable snapshots. ## Quick Start Ask the assistant to kick off a new project from your uploaded PRD, SRS, and WBS documents and build the execution context pack before writing code.

Frequently Asked Questions about dev-kickoff-edho-ferdian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a development project from a PRD or SRS document?

Provide your specification documents (PRD, SRS, WBS, tech spec, RFC, or ADRs) and ask for a project kickoff. The skill classifies each document by role, cross-validates them for conflicts, extracts a binding Project Decision Register, then builds an execution plan before writing any code.

What documents do I need for a project kickoff with an AI coding assistant?

At minimum you need documents covering ARCHITECTURE (tech spec, SDD, or ADRs) and WORK_PLAN (WBS, sprint plan, or issue list). Other roles like PRODUCT_INTENT and BEHAVIOR_SPEC are recommended; missing ones can be derived as clearly labeled provisional plans pending your approval.

Can I resume an interrupted AI coding project in a new session?

Yes. The skill maintains a /project-memory/ directory with a progress ledger and Session Snapshots. In a new session with repo access it reads those files directly; in pure chat you paste the latest snapshot plus the Execution Context Pack and say resume.

Does this work with Cursor, Copilot, and other AI coding tools?

Yes. Phase 2 generates tool-specific variants: CLAUDE.md for Claude Code, .cursorrules or AGENTS.md for Cursor, copilot-instructions.md for GitHub Copilot, and a universal context-pack.md for any chat-based AI. Existing files are merged, never overwritten.

What happens when specification documents conflict with each other?

Conflicts are reported as BLOCKER, WARNING, or NOTE findings rather than resolved silently. BLOCKERs, such as a task that violates a declared non-goal, require your explicit decision before execution proceeds, and the outcome is recorded in the decision register.

When should I not use a full project kickoff workflow?

Skip it for trivial one-line edits, clearly scoped bug fixes with a known reproduction, or active debugging sessions where the next step is itself the clarification. The full intake and validation ceremony adds value only when real specification ambiguity exists.