skills.rest
bingeli1379
bingeli1379COMMUNITY
Explore all skills by this author →
GitHub

esdd-complete

Extract knowledge, update docs, and clean up artifacts for completed changes.

2|Updated Apr 6, 2026
Search Tags:#automation#knowledge-extraction#git-history#feature-spec#change-management#docs-update
One-click install
npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill esdd-complete
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: esdd-complete
Source: https://github.com/bingeli1379/eli-claude-marketplace/tree/main/plugins/eureka-sdd/skills/esdd-complete
Command: npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill esdd-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complete a change by extracting valuable knowledge, updating project docs, and then deleting the change artifacts.

Core Features & Use Cases

  • Batch-complete all fully finished changes when no name is provided.
  • Complete a single specified change, performing knowledge extraction, documentation updates, and artifact cleanup.
  • Provides status visibility for tasks and supports optional user confirmation when required.

Quick Start

Run /esdd-complete with a change name to complete that change, or omit the name to batch-complete all finished changes.

Frequently Asked Questions about esdd-complete

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

FAQPage Schema
How do I automate change completion and extract knowledge from completed feature specs?▼

To automate change completion, you can use a tool that reads proposal.md, design.md, tasks.md, and git history to extract knowledge. It then updates project docs and cleans up the change artifacts automatically.

Can I batch-complete multiple fully finished feature spec changes at once?▼

Yes, you can batch-complete multiple changes by running the process without specifying a change name. It automatically identifies and processes all fully completed feature spec changes in the directory.

How does knowledge extraction from git history and feature specs update project documentation?▼

Knowledge extraction works by analyzing git history alongside feature spec files like specs/spec.md. It records the extracted knowledge into context.md and related docs, yielding pointers for future audit and reference.

What files are required to run an automated change completion process for feature specs?▼

The change completion process requires feature spec artifacts including proposal.md, design.md, tasks.md, and specs/*/spec.md, along with their corresponding git history, to accurately determine the scope.

What is the best way to clean up feature spec artifacts after a change is completed?▼

The best way to clean up artifacts is to use an automated change completion process that extracts valuable knowledge and updates project docs first, then safely deletes the finished feature spec change artifacts.

Does change management automation support optional user confirmation before deleting feature spec artifacts?▼

Yes, change management automation supports optional user confirmation when required. It provides status visibility for tasks before proceeding with knowledge extraction and artifact cleanup.

Related Skills

Explore More Software Engineering Skills→
bingeli1379bingeli1379
2

esdd-validate

Validate proposal.md, design.md, tasks.md, and specs for a change.

Community
Advanced
CoachSteffCoachSteff
1

knowledgebase

Organize institutional knowledge with categories, tags, versioning, and full-text search.

Community
Advanced
dayvidphamdayvidpham
1

architect-request-review

Spawn three specialized reviewers to evaluate architectural proposals.

Community
Advanced
hungv47hungv47
14

clean-code

Audit and refactor existing code for readability without changing behavior.

Community
Intermediate