implementation-plan

Generates repository-grounded implementation plans with synchronized plan, context, and task artifacts.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill implementation-plan-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/implementation-plan
Command: npx skills add https://github.com/islamu-ngo/Event --skill implementation-plan-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It prevents memory-based planning by forcing every implementation plan to be grounded in verified repository evidence, producing consistent plan, context, and task documents before any code is written. ## Core Features & Use Cases - Evidence-First Investigation: Verifies every claimed file, symbol, test, and contract against the actual repository before designing future state. - Dev-Doc Triad Generation: Writes synchronized plan.md, tasks.md, and context.md artifacts under dev/active/<task>/ with strict separation of concerns. - Behavioral Contracts & Phased Verification: Defines RFC 2119 behavioral scenarios, invariant-first test slicing, and per-phase commit contracts following Conventional Commits. - Use Case: Ask for an implementation plan for a new RSVP feature and receive a complete, reviewable plan with current-state evidence, phased tasks, and commit contracts ready for approval. ## Quick Start Ask the agent to create an implementation plan for the feature or refactor you want, providing the task name and scope.

Frequently Asked Questions about implementation-plan

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

FAQPage Schema
How do I create an implementation plan for a new feature?▼

Request an implementation plan with a clear task description. The skill derives a kebab-case task name, verifies repository evidence, resolves open questions through structured intake, and writes plan, context, and tasks files under dev/active/<task>/.

What artifacts does an implementation planning workflow produce?▼

It produces three synchronized files: a plan with architecture and behavioral scenarios, a tasks file as the hot execution ledger with checkboxes and commit contracts, and a context file for session memory and handoffs.

Does this planning workflow write or modify application code?▼

No. Planning is strictly decoupled from execution. It never creates branches, worktrees, or code changes; it only produces planning artifacts in dev/active/ on the main workspace for user review and approval.

When should I skip persistent planning documents?▼

Skip them for atomic changes that can be implemented and verified safely in one short slice. Use the full triad for complex, cross-layer, multi-session, or multi-contributor work.

Why must plans verify repository evidence before designing?▼

Memory-based planning turns assumptions into false implementation facts. Verifying every path, symbol, test, and contract against the actual repository ensures the plan reflects current reality and prevents rework during implementation.