Verified:GitHub

get-shit-done

Orchestrate software project milestones, phases, and atomic plans via slash commands.

Updated Feb 26, 2026

Search Tags:#project management #workflow automation #context engineering #agent orchestration #spec-driven development #meta-prompting

Ready to run

npx skills add https://github.com/keremtoker468-dotcom/restoran --skill get-shit-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: get-shit-done
Source: https://github.com/keremtoker468-dotcom/restoran/tree/main/.claude/skills/get-shit-done
Command: npx skills add https://github.com/keremtoker468-dotcom/restoran --skill get-shit-done

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill tackles context rot by orchestrating complex projects through milestones, phases, and atomic plans, ensuring focused execution and persistent state.

Core Features & Use Cases

Project Orchestration: Manages project lifecycle from ideation to completion via slash commands.
Context Engineering: Solves context rot by breaking work into manageable chunks.
Spec-Driven Development: Enforces requirements and plans before execution.
Use Case: Initiate a new project with /gsd:new-project, plan and execute phases with /gsd:plan-phase and /gsd:execute-phase, and track progress with /gsd:progress.

Quick Start

Use the get-shit-done skill to start a new project by typing /gsd:new-project.

Frequently Asked Questions about get-shit-done

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

FAQPage Schema

How do I prevent context rot when managing complex software projects with AI agents?▼

Spec-driven development enforces strict requirements and plans before any code execution begins. It manages project lifecycles through structured slash commands, ensuring focused execution and persistent state across milestones and phases.

How do I orchestrate milestones and phases for a new software project?▼

You orchestrate milestones and phases by initiating the project with a structured slash command, then sequentially planning and executing individual phases to maintain a persistent project state from ideation to completion.

What is meta-prompting for workflow automation in software engineering?▼

Meta-prompting for workflow automation is a technique that structures project execution through engineered context and spec-driven commands. It guides agent orchestration by enforcing requirements before development across complex project phases.

Can I use spec-driven development for debugging and codebase mapping?▼

Yes, spec-driven development workflows support debugging, codebase mapping, and research tasks. These features are integrated directly into the structured phase execution and verification lifecycle to maintain context integrity.

Do I need external dependencies to enforce context engineering in my workflow?▼

No external dependencies are required. The workflow relies entirely on internal scripts, references, and templates to engineer context, orchestrate agents, and manage project state without integrating outside libraries.

When should I avoid breaking work into atomic plans for agent orchestration?▼

You should avoid breaking work into atomic plans for simple, single-step tasks that do not suffer from context rot. The overhead of milestone planning and spec-driven constraints provides no benefit for trivial, isolated code modifications.