Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.
Install Spk Start First Feature
$ npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install spec-kitty/spec-kitty spk-start-first-feature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/charter/offering/skills/spk-start-first-feature .claude/skills/spk-start-first-feature && rm -rf skills-srcUse ~/.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/
Install the "spk-start-first-feature" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature into .claude/skills/spk-start-first-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spk-start-first-feature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-featureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install spec-kitty/spec-kitty spk-start-first-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/charter/offering/skills/spk-start-first-feature .agents/skills/spk-start-first-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spk-start-first-feature" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature into .agents/skills/spk-start-first-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spk-start-first-feature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install spec-kitty/spec-kitty spk-start-first-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/charter/offering/skills/spk-start-first-feature .cursor/skills/spk-start-first-feature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spk-start-first-feature" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature into .cursor/skills/spk-start-first-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spk-start-first-feature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/spec-kitty/spec-kitty.git --path src/charter/offering/skills/spk-start-first-feature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install spec-kitty/spec-kitty spk-start-first-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/charter/offering/skills/spk-start-first-feature .gemini/skills/spk-start-first-feature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spk-start-first-feature" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature into .gemini/skills/spk-start-first-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spk-start-first-feature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install spec-kitty/spec-kitty spk-start-first-featureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/charter/offering/skills/spk-start-first-feature .github/skills/spk-start-first-feature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spk-start-first-feature" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature into .github/skills/spk-start-first-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spk-start-first-feature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install spec-kitty/spec-kitty spk-start-first-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/charter/offering/skills/spk-start-first-feature .opencode/skills/spk-start-first-feature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spk-start-first-feature" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature into .opencode/skills/spk-start-first-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spk-start-first-feature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
spk-start-first-feature- GitHub stars
- 1.7k
- Token cost
- ~302 tokens
- SKILL.md length
- 131 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.
- Works in 8 steps: Verify install and agent surface with… → Create or select the mission with… → Build the plan with /spec-kitty.plan. → …
- Tasks that involve Retrospectives
- SKILL.md covers Workflow and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Spk Start First Feature is an agent skill from spec-kitty/spec-kitty. Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.
Its SKILL.md is about 300 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 Product & Project Management, covering Retrospectives. The repository describes itself as: Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and… The licence is MIT.
When your agent uses it
- Tasks that involve Retrospectives
Example prompts
- “/spk-start-first-feature”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Verify install and agent surface with spk-admin-setup-doctor if commands or
- Create or select the mission with /spec-kitty.specify.
- Build the plan with /spec-kitty.plan.
- Produce work packages with /spec-kitty.tasks or the outline/packages/finalize
- Advance work with spk-run-next.
- Drive implementation/review loops with spk-run-implement-review.
- Close with spk-gate-accept, then spk-gate-merge.
- Finish post-merge checks with spk-gate-mission-review and
What it can do on your machine
Read from SKILL.md and the folder at commit 4cabb90. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
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
Spk Start First Feature loads about 302 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 131 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 spec-kitty/spec-kitty at commit 4cabb90, republished under its MIT licence (© spec-kitty). 131 words, ~302 tokens.
Download SKILL.mdSave it as
.claude/skills/spk-start-first-feature/SKILL.md (or your agent's skills folder).- name
- spk-start-first-feature
- description
- Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.
spk-start-first-feature
Use this skill when a user wants to start their first Spec Kitty mission or feature and needs the end-to-end path.
Workflow
- Verify install and agent surface with
spk-admin-setup-doctorif commands or skills are missing. - Create or select the mission with
/spec-kitty.specify. - Build the plan with
/spec-kitty.plan. - Produce work packages with
/spec-kitty.tasksor the outline/packages/finalize split when the project uses staged task authoring. - Advance work with
spk-run-next. - Drive implementation/review loops with
spk-run-implement-review. - Close with
spk-gate-accept, thenspk-gate-merge. - Finish post-merge checks with
spk-gate-mission-reviewandspk-gate-retrospective.
Guardrails
- Keep the user on one mission until a blocker requires a different route.
- Treat generated runtime prompt files as authoritative for the current action.
- Do not skip review, accept, or merge gates just because implementation appears complete.
© spec-kitty, MIT. 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 src/charter/offering/skills/spk-start-first-feature of spec-kitty/spec-kitty.
Open the folder on GitHubat commit 4cabb90
Compare with similar skills
Spk Start First Feature 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spk Start First Feature this skillspec-kitty/spec-kitty | 1.7k | — | ~302 | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| After Action Reportrampstackco/claude-skills | 940 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 340 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1k | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
After Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
Deck Retro
asheshgoplani/agent-deck
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.
Dough Execution Retrospective
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
More from spec-kitty/spec-kitty
All 50 skills in this repoSpec Kitty Setup Doctor
spec-kitty/spec-kitty
Install, verify, and recover the modern Spec Kitty 2.0.11+ operating surface.
Spk Doctrine Show Me
spec-kitty/spec-kitty
Explain Spec Kitty work with compact, checkable visuals. An agent skill from spec-kitty/spec-kitty.
Spec Kitty Git Workflow
spec-kitty/spec-kitty
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit…
Spec Kitty Glossary Context
spec-kitty/spec-kitty
Curate and apply canonical terminology across Spec Kitty missions.
Spec Kitty Mission System
spec-kitty/spec-kitty
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are…
Spec Kitty Orchestrator API Operator
spec-kitty/spec-kitty
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI.
Related
Categories
Questions about Spk Start First Feature
What does Spk Start First Feature do?
Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective. Spk Start First Feature is an agent skill from spec-kitty/spec-kitty. Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.
When should I use Spk Start First Feature?
Spk Start First Feature fits situations like: tasks that involve Retrospectives.
How do I install Spk Start First Feature in Claude Code?
Run `npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a claude-code`. Or copy the skill folder (src/charter/offering/skills/spk-start-first-feature in spec-kitty/spec-kitty) into .claude/skills/spk-start-first-feature in your project. Claude Code loads it when a task matches its description.
How do I install Spk Start First Feature in Codex?
Run `npx skills add spec-kitty/spec-kitty --skill spk-start-first-feature -a codex`. Or copy the skill folder (src/charter/offering/skills/spk-start-first-feature in spec-kitty/spec-kitty) into .agents/skills/spk-start-first-feature in your project. Codex loads it when a task matches its description.
Can I use Spk Start First Feature 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 spec-kitty/spec-kitty --skill spk-start-first-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spk-start-first-feature, .gemini/skills/spk-start-first-feature, .github/skills/spk-start-first-feature and .opencode/skills/spk-start-first-feature in your project.
What does Spk Start First Feature need to run?
SKILL.md names no scripts, command-line tools or credentials: Spk Start First Feature is instructions for the agent only.
Does Spk Start First Feature 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 Spk Start First Feature safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Spk Start First Feature use?
Spk Start First Feature is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Spk Start First Feature use?
About 302 tokens (SKILL.md is roughly 1.2k 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 Spk Start First Feature?
Skills that share tags, products or a category with Spk Start First Feature: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars), After Action Report (rampstackco/claude-skills, 940 stars) and Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 340 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spk Start First Feature?
spec-kitty (a GitHub organization) maintains it in spec-kitty/spec-kitty, which has 1,677 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.
Source: spec-kitty/spec-kitty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.