Convert a GSD-2 project back to GSD v1 format while preserving completion status, research files, and summaries. Preview the files and migration statistics before confirming the conversion, with the original project directory left intact.
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
Review the instructions the agent will receive before you install.
Maps the GSD-2 hierarchy (Milestone → Slice → Task) to the GSD v1 hierarchy (Milestone sections in ROADMAP.md → Phase → Plan), preserving completion state, research files, and summaries.
CJS-only: from-gsd2 is not on the gsd-sdk query registry; call gsd-tools.cjs as shown below (see docs/CLI-TOOLS.md).
</objective>
Locate the .gsd/ directory — check the current working directory (or --path argument):
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2 --dry-run
If no .gsd/ is found, report the error and stop.
Show the dry-run preview — present the full file list and migration statistics to the user. Ask for confirmation before writing anything.
Run the migration after confirmation:
node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" from-gsd2
Use --force if .planning/ already exists and the user has confirmed overwrite.
Report the result — show the filesWritten count, planningDir path, and the preview summary.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.
Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.
Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.
Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.