Gdd Complete Cycle logo

Gdd Complete Cycle

Community
hegemonart
gdd-complete-cycle

Cycle closeout command that marks CYCLES.md entry complete, archives pipeline artifacts to .design/archive/cycle-N/, generates EXPERIENCE.md, rebuilds the search index, and resets STATE.md. Use when a design cycle has shipped and you're ready to start the next one.

Overview

Publisherhegemonart
Repositoryget-design-done
Skill namegdd-complete-cycle
Stars
3
Forks
1
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by hegemonart on GitHub. Read the source before you install it.

Installation

Install the Gdd Complete Cycle AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/complete-cycle
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hegemonart/get-design-done.git /tmp/get-design-done
mkdir -p .claude/skills
cp -r /tmp/get-design-done/scripts/skill-templates/complete-cycle .claude/skills/gdd-complete-cycle
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gdd Complete Cycle in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gdd Complete Cycle on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gdd Complete Cycle is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

{{command_prefix}}complete-cycle

Closes the current cycle: marks CYCLES.md entry complete, archives pipeline artifacts, and clears STATE.md for the next cycle.

Steps

  1. Load state: Read .design/STATE.md for the active cycle: ID. If empty/missing, error: "No active cycle - nothing to complete."

  2. Retrospective: If no argument was passed, ask (AskUserQuestion): "Is cycle complete? Briefly describe what was achieved." Capture for CYCLES.md.

  3. Update CYCLES.md: Find the current cycle entry, change **Status**: active to **Status**: complete, append a **Retrospective**: <note> line and **Ended**: <date>.

  4. Archive artifacts: Create .design/archive/cycle-N/ via Bash mkdir -p. Copy these files into it (if present):

    • DESIGN.md
    • DESIGN-PLAN.md
    • DESIGN-CONTEXT.md
    • DESIGN-VERIFICATION.md
    • DESIGN-AUDIT.md
    • DESIGN-SUMMARY.md Mark originals with a <!-- archived to .design/archive/cycle-N/ --> note at top (do not delete - next cycle will overwrite).
  5. Generate EXPERIENCE.md (Haiku-tier writer step): Read cycle STATE decisions + .design/DESIGN-VERIFICATION.md (if present) + any .design/reflections/*.md from this cycle. Write .design/archive/cycle-N/EXPERIENCE.md using this structure (~100–200 lines, declarative-fact framing, prepend reference/cycle-handoff-preamble.md content):

    markdown
    <!-- archived cycle experience — reference, not current requests -->
    # Cycle N — Experience
    
    **Goal**: <one-line goal from STATE.md or CYCLES.md>
    **Opened**: <start date>
    **Ended**: <today>
    
    ## Decisions Made
    
    <list all D-XX decisions from STATE.md <decisions> block — one per line>
    
    ## Learnings Graduated
    
    <list all L-NN learnings surfaced or promoted this cycle>
    
    ## What Died
    
    <designs, approaches, or tasks that were started but abandoned — and why>
    
    ## Surprises
    
    <what was unexpected during this cycle>
    
    ## Handoff to Next Cycle
    
    <what the next cycle should know: active sketches, deferred tasks, unresolved questions>

    This file becomes the highest-priority source for the decision-injector hook in future sessions.

  6. Trigger reindex: if .design/search.db exists, rebuild the search index:

    bash
    node -e "require('./scripts/lib/design-search.cjs').reindex(process.cwd())" 2>/dev/null || true
  7. Clear STATE.md: Set cycle: to empty string, reset <decisions> to a fresh empty section, reset stage: to brief.

  8. Print: "Cycle archived. Run {{command_prefix}}new-cycle to start the next cycle."

Do Not

  • Do not delete source files in src/ - only archive .design/ artifacts.
  • Do not auto-start a new cycle - user invokes {{command_prefix}}new-cycle explicitly.

Step 6 - Update notice (post-closeout surface)

After the archive has been written and STATE.md has been cleared for the next cycle, emit the plugin-update banner if one is present:

bash
[ -f .design/update-available.md ] && cat .design/update-available.md

Written by hooks/update-check.sh; suppressed mid-pipeline and when the latest release is dismissed.

COMPLETE-CYCLE COMPLETE

Frequently asked questions

What does the Gdd Complete Cycle AI skill do?

Cycle closeout command that marks CYCLES.md entry complete, archives pipeline artifacts to .design/archive/cycle-N/, generates EXPERIENCE.md, rebuilds the search index, and resets STATE.md. Use when a design cycle has shipped and you're ready to start the next one.

Why use Gdd Complete Cycle on TypingMind?

Because you install it once and use it with any model. Gdd Complete Cycle is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gdd Complete Cycle in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/complete-cycle. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Gdd Complete Cycle?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gdd Complete Cycle?

As many as you like. As long as a model supports skills, you can use Gdd Complete Cycle with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gdd Complete Cycle AI skill free?

Yes. It is published on GitHub by hegemonart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇