create-plan-gitlab SKILL.md skillA

create-plan-gitlab from codelytv/agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add codelytv/agent-harness/create-plan-gitlab@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
codelytv/agent-harness
Path
.agents/skills/create-plan-gitlab/SKILL.md
Versions recorded
2
Latest version
v1.0, committed Nov 17, 2026
First version recorded
Nov 17, 2026
Size
7,728 bytes
Repository stars
319
License
none declared

Create a plan for the specified task and store it as GitLab issues in the repository of the current working directory. Given the URL of a GitLab issue, it turns that issue into the parent "plan" issue (Goal, Context and a checklist of phases) and creates one child issue per phase, linking every phase to the parent with GitLab related-issue links. Stops for user approval before creating any issue. After creation, the plan is meant to be implemented with the implement-plan-phase-gitlab skill.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 🧠 How to create a plan

> [!CRITICAL]
> Do NOT create or edit any GitLab issue until the user has agreed on the specific public contracts to be considered and the implementation phases. Propose first, get approval, then create the issues.

The structure of a plan, its sections and the rules to shape them are defined in [`references/plan-guidelines.md`](references/plan-guidelines.md). Read it before proposing anything.

## 🎯 Input

This skill is invoked as `/create-plan-gitlab <gitlab-issue-url>`.

- `<gitlab-issue-url>` is the URL of the GitLab issue describing the task to plan. **This issue becomes the parent "plan" issue.** GitLab issue URLs look like `https://gitlab.com/<namespace>/<project>/-/issues/<iid>`.
- If no URL is provided, ask the user for it before doing anything else.

## 🗂️ Repository

All the plan lives as GitLab issues in the repository of the current working directory. Never hardcode a repository: let `glab` resolve it from the local Git remote.

```bash
glab issue view <iid>
glab issue create --title "..." --description "..." --linked-issues <parent-iid> --link-type relates_to --yes
glab issue update <iid> --description "..."
```
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_op5rv7yoerdzih6e/21a5f12fa7bdd4098e6a90dd84d131294e6df366b358868cb5f64a6e327914df.json

Then /plugin install create-plan-gitlab@markdownregistry-op5rv7yoerdzih6e in Claude Code. It installs v1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add codelytv/agent-harness/create-plan-gitlab@sha256:21a5f12fa7bdd409

The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_op5rv7yoerdzih6e.svg)](https://markdownregistry.com/a/art_op5rv7yoerdzih6e)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in codelytv/agent-harness/create-plan-gitlab since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of create-plan-gitlab from somewhere else? Ask it: where did my create-plan-gitlab come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, all committed on Nov 17, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v1.0 latest2026-11-17 d934729 7,728 BA view · diff
v1.02026-11-17 354aa27 7,724 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (7728 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

codelytv/agent-harness · 319 stars · license none declared · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_op5rv7yoerdzih6e
GET https://markdownregistry.com/api/v1/resolve?ref=codelytv/agent-harness/create-plan-gitlab
GET https://markdownregistry.com/api/v1/blob/21a5f12fa7bdd4098e6a90dd84d131294e6df366b358868cb5f64a6e327914df

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from codelytv/agent-harness

conventions-to-rules SKILL.md skill
codelytv/agent-harness · .agents/skills/conventions-to-rules/SKILL.md · Find the jobs the code does in more than one way and enforce the current way with deterministic rules that fail in…
v1.0 · audit A · 319 stars
create-doc SKILL.md skill
codelytv/agent-harness · .agents/skills/create-doc/SKILL.md · Deprecated: use create-rule instead. Create new documentation based on the current conversation context.
v1.0 · audit A · 319 stars
create-plan-github SKILL.md skill
codelytv/agent-harness · .agents/skills/create-plan-github/SKILL.md · Create a plan for the specified task and store it as GitHub issues in the repository of the current working directory…
v1.0 · audit A · 319 stars
create-plan-subagents SKILL.md skill
codelytv/agent-harness · .agents/skills/create-plan-subagents/SKILL.md · Create a plan for the specified task.
v1.0 · audit A · 319 stars
create-plan SKILL.md skill
codelytv/agent-harness · .agents/skills/create-plan/SKILL.md · Create a plan for the specified task.
v1.0 · audit A · 319 stars
create-pull-request SKILL.md skill
codelytv/agent-harness · .agents/skills/create-pull-request/SKILL.md · Write the title and the description of a pull request following the team template, with before/after evidence of the…
v1.0 · audit A · 319 stars
create-rule SKILL.md skill
codelytv/agent-harness · .agents/skills/create-rule/SKILL.md · Turn one new convention into a deterministic rule (linter config, custom lint rule or test) that fails in seconds. When…
v1.0 · audit A · 319 stars
deterministify SKILL.md skill
codelytv/agent-harness · .agents/skills/deterministify/SKILL.md · Turn the conventions of a repository into deterministic rules (linter config, custom lint rules, tests) that fail in…
v1.0 · audit A · 319 stars
docs-to-rules SKILL.md skill
codelytv/agent-harness · .agents/skills/docs-to-rules/SKILL.md · Turn the written conventions of a repository (docs, AGENTS.md, ADRs, guidelines) into deterministic rules that fail in…
v1.0 · audit A · 319 stars
git-commit SKILL.md skill
codelytv/agent-harness · .agents/skills/git-commit/SKILL.md · Create a git commit following the team's Conventional Commit conventions. Use when the user asks to commit changes or…
v1.0 · audit A · 319 stars
implement-plan-phase-github SKILL.md skill
codelytv/agent-harness · .agents/skills/implement-plan-phase-github/SKILL.md · Implement one phase of a plan stored as GitHub issues in the repository of the current working directory. Given the URL…
v1.0 · audit A · 319 stars
implement-plan-phase-gitlab SKILL.md skill
codelytv/agent-harness · .agents/skills/implement-plan-phase-gitlab/SKILL.md · Implement one phase of a plan stored as GitLab issues in the repository of the current working directory. Given the URL…
v1.0 · audit A · 319 stars

Every file in codelytv/agent-harness

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.