Skip to content
Skills Library
Programming · Planning

context-kit

/context-kit

Spec-first project start. Use when the user types `discuss [idea]` (talk an idea through before any code - one question at a time, 2-3 approaches, a design approved section by section) or `context kit` (turn the approved design into seven context files and the first feature specs, then hold all code until the user approves them), or asks to plan or spec a new project or feature before building it.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
11
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Spec-first project start. Use when the user types `discuss [idea]` (talk an idea through before any code - one question at a time, 2-3 approaches, a design approved section by section) or `context kit` (turn the approved design into seven context files and the first feature specs, then hold all code until the user approves them), or asks to plan or spec a new project or feature before building it.

Original author description

Spec-first project start. Use when the user types `discuss [idea]` (talk an idea through before any code - one question at a time, 2-3 approaches, a design approved section by section) or `context kit` (turn the approved design into seven context files and the first feature specs, then hold all code until the user approves them), or asks to plan or spec a new project or feature before building it.

How it works

  1. Where things live
  2. Route the request
  3. Both commands
  4. After approval
Original SKILL.md headings · 35 lines, 409 words
SKILL.md preview
---
name: context-kit
description: Spec-first project start. Use when the user types `discuss [idea]` (talk an idea through before any code - one question at a time, 2-3 approaches, a design approved section by section) or `context kit` (turn the approved design into seven context files and the first feature specs, then hold all code until the user approves them), or asks to plan or spec a new project or feature before building it.
---

# Context kit

Two commands, one gate.

| Command          | Does                                                                     | Writes          |
| ---------------- | ------------------------------------------------------------------------ | --------------- |
| `discuss [idea]` | Talks the idea through until the user approves a design, or drops the idea | Nothing         |
| `context kit`    | Fills the seven context files and the first feature specs from that design | `context/`, plus a pointer in the instructions file |

**The gate**: until the user approves the filled specs, every file you write lives in the project's `context/` folder, apart from the short pointer section `context kit` adds to the instructions file so later sessions find the specs. Code, scaffolding, package installs and config come after approval, one feature at a time, built against its spec.

## Where things live

- **Templates**: `context/` beside this file, the seven files plus `feature-specs/_template.md`. Read them fresh from here every time; they are the source of truth.
- **The project's copy**: `context/` at the project root, which is the working directory unless the user names another folder.
- **The instructions file**: the file your agent reads at the start of every session, at the project root: `CLAUDE.md` in Claude Code, `GEMINI.md` in Gemini CLI, `AGENTS.md` in Codex and most other agents.

## Route the request

- `discuss [idea]`: read `discuss.md` (beside this file) and follow it.
- `context kit`: read `fill.md` (beside this file) and follow it. It starts by checking that a design was approved, and sends you to `discuss.md` when none was.
- A new feature in a project whose `context/` is already filled: `discuss` scoped to that one feature, then `context kit` adds its spec. `fill.md` covers this case.
- The user wants only the blank templates: copy this skill's `context/` into the project unfilled, and stop.

## Both commands

- **Speak the user's language** (BM, English, rojak: match them). Keep file names, template headings and IDs (`F-01`, `AC-1`, `D-1`) exactly as the templates have them, because the method and other tools rely on them.
- **One question per message**, then wait for the answer.
- **Every decision has an owner**: the user's answer, a default the user approved, or a logged `⚠️ Assumed`. A gap you notice becomes a question or a logged assumption, so nothing is decided silently.

## After approval

Build one feature at a time by the project's `context/ai-workflow-rules.md`: input coverage check, build, verify every AC the way the project's workflow depth requires, then update `progress-tracker.md`.
Files in this package (11)
  • SKILL.md 3 KB
  • discuss.md 7 KB
  • fill.md 10 KB
  • context/ai-workflow-rules.md 4 KB
  • context/architecture.md 2 KB
  • context/code-standards.md 3 KB
  • context/design.md 2 KB
  • context/progress-tracker.md 1 KB
  • context/project-overview.md 3 KB
  • context/ui-context.md 4 KB
  • context/feature-specs/_template.md 2 KB

Versions

The database has no other skills named context-kit.

Database snapshot: 13.11.2026 · package version a928b0319316 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100spec-kit
    Spec Kit is GitHub's open-source toolkit that installs a set of agent commands into a project so a coding agent builds features from a written specification: specify, plan, tasks, implement, then converge against the spec. It also ships optional processes for bug fixing and for…
  • 100feature-implement
    [Implementation] Use when the user asks to build a feature from an idea or description with no plan file yet: research and trace the code, create and get the plan approved, build each phase with its tests, review, verify once, sync specs and docs. Existing plan: plan --mode=execute.
  • 100spec-kit-builder
    Guides a person step by step through building a whole software project with GitHub Spec Kit. Finds or creates the project documents, explains the project back in simple words, checks and installs Git, uv and Spec Kit with the user's consent, runs specify init, then runs…
  • 100blueprint
    Use when a written feature spec needs its technical plan: \"plan this spec\", \"how should we build this spec?\", \"make the technical plan for this feature\", a spec in specs/ with no plan.md yet, or a plan that a spec or constitution change has made stale. Not for a feature…
  • 100import-spec
    Imports a spec-kit feature spec into Shipyard in place of brainstorming. Use when a spec-kit feature directory with spec.md exists.
  • 100spec-driven-development
    Turns an approved idea or ticket into spec, plan, and task files saved in the repo, then executes them one task at a time with a progress log. Use to write a spec, plan a feature, break work into tasks, or resume multi-session work.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.