Agent skill

Continue Spec

by karanhudia in karanhudia/borg-ui

Continue a multi-phase engineering spec from its progress table.

AGPL-3.0Auto-check: notesAgent Workflows

Install Continue Spec

skills CLI
$ npx skills add karanhudia/borg-ui --skill continue-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install karanhudia/borg-ui continue-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/continue-spec .claude/skills/continue-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
continue-spec
GitHub stars
1.7k
Token cost
~592 tokens
SKILL.md length
286 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Continue a multi-phase engineering spec from its progress table.

  • Works in 3 steps: If an argument is given, it is the spec… → Otherwise, use the newest file under… → If none exists, tell the user and stop.
  • The user says /continue-spec
  • SKILL.md covers Resolve the spec, Follow the spec's own protocol and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Continue Spec is an agent skill from karanhudia/borg-ui. Continue a multi-phase engineering spec from its progress table. Use when the user says /continue-spec, "continue the spec", "continue the operations feature", or asks what the next phase is. Runs the next step (plan, implement, review) in this session on the model the spec names, stopping at the spec's gates. Never uses subagents.

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Subagents. The repository describes itself as: Replace complex Borg Backup terminal commands with a beautiful web UI. Create, schedule, and restore backups with just a few clicks. The licence is AGPL-3.0.

When your agent uses it

  • The user says /continue-spec
  • Continue the spec
  • Continue the operations feature
  • Asks what the next phase is

Example prompts

  • “continue the spec”
  • “continue the operations feature”
  • “/continue-spec”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Edit, Write, AskUserQuestion, Skill

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. If an argument is given, it is the spec path.
  2. Otherwise, use the newest file under docs/engineering/specs/ that
  3. If none exists, tell the user and stop.

What it can do on your machine

Read from SKILL.md and the folder at commit 196a74a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Edit
    • Write
    • AskUserQuestion
    • Skill

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Continue Spec loads about 592 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 286 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~592

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Edit, Write, AskUserQuestion, Skill

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from karanhudia/borg-ui at commit 196a74a, republished under its AGPL-3.0 licence (© karanhudia). 286 words, ~592 tokens.

Download SKILL.mdSave it as .claude/skills/continue-spec/SKILL.md (or your agent's skills folder).
name
continue-spec
description
Continue a multi-phase engineering spec from its progress table. Use when the user says /continue-spec, "continue the spec", "continue the operations feature", or asks what the next phase is. Runs the next step (plan, implement, review) in this session on the model the spec names, stopping at the spec's gates. Never uses subagents.
allowed-tools
Read, Bash, Edit, Write, AskUserQuestion, Skill

Continue a spec

You do the next step yourself, in this session. Do not dispatch subagents; the owner has ruled them out on cost. The spec tells you which model each step wants; you check the model you are running on and ask before proceeding if it differs.

Resolve the spec

  1. If an argument is given, it is the spec path.
  2. Otherwise, use the newest file under docs/engineering/specs/ that contains a heading matching ## <n>. Working this spec.
  3. If none exists, tell the user and stop.

Current default: docs/engineering/specs/2026-09-03-repository-operations-and-archive-history.md.

Follow the spec's own protocol

Read the spec in full. Its "Working this spec" section defines the progress table, the continuation protocol, the review focus per phase, and the gates. Follow it exactly. In short:

  1. Find the first phase not done in the progress table.
  2. Work out the step from its status and the model that step wants from the phases table.
  3. Gate G0: compare with the model this session runs on. If different, ask the user to switch with /model and rerun, or to continue anyway. Wait for the answer.
  4. Do the step in this session:
    • plan: superpowers:writing-plans, then gate G1;
    • implement: branch, superpowers:executing-plans with superpowers:test-driven-development, then superpowers:verification-before-completion, then gate G2;
    • review: /code-review high against the listed spec sections, findings only, then gate G3.
  5. Update the progress table immediately after every state change.

Rules

  • Never commit, push, or merge without the gate answer. See .claude/instructions.md.
  • Never re-open a decision recorded in the spec's Appendix B. Escalate to gate G5 instead.
  • The spec wins when the plan and the code disagree.
  • Report back in plain language: which phase, which step, what was done, what the user needs to decide now.

© karanhudia, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/continue-spec of karanhudia/borg-ui.

Open the folder on GitHubat commit 196a74a

Compare with similar skills

Continue Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Continue Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Continue Spec this skillkaranhudia/borg-ui1.7k—~592Automated safety check: NotesAGPL-3.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25841 repos~1.5kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~12kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 41 repos~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~12k tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from karanhudia/borg-ui

  • Borg Live Debug

    karanhudia/borg-ui

    Live Borg debugging by exec-ing into the borg-web-ui Docker container.

    1.7k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check: notes
  • Pull

    karanhudia/borg-ui

    Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch).

    1.7k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Push

    karanhudia/borg-ui

    Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.

    1.7k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Linear

    karanhudia/borg-ui

    Use Symphony's lineargraphql client tool for raw Linear GraphQL operations such as comment editing and upload flows.

    1.7k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Continue Spec

What does Continue Spec do?

Continue a multi-phase engineering spec from its progress table. Continue Spec is an agent skill from karanhudia/borg-ui. Continue a multi-phase engineering spec from its progress table.

When should I use Continue Spec?

Continue Spec fits situations like: the user says /continue-spec; continue the spec; continue the operations feature; asks what the next phase is.

How do I install Continue Spec in Claude Code?

Run `npx skills add karanhudia/borg-ui --skill continue-spec -a claude-code`. Or copy the skill folder (.claude/skills/continue-spec in karanhudia/borg-ui) into .claude/skills/continue-spec in your project. Claude Code loads it when a task matches its description.

How do I install Continue Spec in Codex?

Run `npx skills add karanhudia/borg-ui --skill continue-spec -a codex`. Or copy the skill folder (.claude/skills/continue-spec in karanhudia/borg-ui) into .agents/skills/continue-spec in your project. Codex loads it when a task matches its description.

Can I use Continue Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add karanhudia/borg-ui --skill continue-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/continue-spec, .gemini/skills/continue-spec, .github/skills/continue-spec and .opencode/skills/continue-spec in your project.

What does Continue Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Continue Spec is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Edit, Write, AskUserQuestion, Skill.

Does Continue Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Continue Spec safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Continue Spec use?

Continue Spec is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Continue Spec use?

About 592 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Continue Spec?

Skills that share tags, products or a category with Continue Spec: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Continue Spec?

karanhudia (a GitHub user) maintains it in karanhudia/borg-ui, which has 1,656 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

Source: karanhudia/borg-ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.