Skip to content
Skills Library
Management & product · Planning

setup

/setup

Step 0 of the SDLC, run once per project. Bootstrap the foundations later steps rely on by recording how the code will be built (architecture, testing, conventions) as committed files, for a new or an existing code base. Use when starting a project, adopting the SDLC in a repo, or when those foundational decisions need to change.

Repository
skills ↗
Licence
MIT
Last repository change
11.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
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.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

Step 0 of the SDLC, run once per project. Bootstrap the foundations later steps rely on by recording how the code will be built (architecture, testing, conventions) as committed files, for a new or an existing code base. Use when starting a project, adopting the SDLC in a repo, or when those foundational decisions need to change.

Arguments

/setup [profile]
Original author description

Step 0 of the SDLC, run once per project. Bootstrap the foundations later steps rely on by recording how the code will be built (architecture, testing, conventions) as committed files, for a new or an existing code base. Use when starting a project, adopting the SDLC in a repo, or when those foundational decisions need to change.

How it works

  1. Mode
  2. Profile
  3. Greenfield mode
  4. Existing mode
  5. Outputs
  6. Rules
Original SKILL.md headings · 48 lines, 547 words
SKILL.md preview
---
name: setup
description: Step 0 of the SDLC, run once per project. Bootstrap the foundations later steps rely on by recording how the code will be built (architecture, testing, conventions) as committed files, for a new or an existing code base. Use when starting a project, adopting the SDLC in a repo, or when those foundational decisions need to change.
argument-hint: [profile]
---

# Setup

Record how this project is built, so every later SDLC step works from written decisions instead of guesses. This skill decides and records. It does not scaffold code.

## Mode

Check whether the repo has source code beyond docs and config.

- No source code: **greenfield mode**.
- Source code present: **existing mode**.
- If `docs/conventions/` already exists, say so and ask whether to revise it or stop.

## Profile

A profile is a markdown file in [profiles/](profiles/) holding the questions to ask and the default conventions for one stack. If `$ARGUMENTS` names one, use it. Otherwise list the available profiles and ask which fits, or whether to build a custom one. Do not assume a stack the user has not chosen.

## Greenfield mode

1. Read the chosen profile.
2. Interview the user through its questions, one topic at a time (architecture, testing, conventions). Offer the profile's default for each, and record the user's choice. Do not decide on the user's behalf.
3. Record each significant choice with its reason (see Outputs).

## Existing mode

1. Use a subagent to survey the code base against the profile's topics (structure, layering, test projects and style, tooling), so the bulk of the reading stays out of this session. Ask it for a summary of what exists, not file dumps.
2. Present what was found, topic by topic. Confirm or correct each with the user. Ask for the reason behind a choice only when it is not evident, and do not invent reasons.
3. Document what exists. Do not flag gaps or propose changes unless the user asks.

## Outputs

Write these in the project, show the user the result, and get a yes before committing.

- `docs/conventions/architecture.md`: the architecture style and structure.
- `docs/conventions/testing.md`: what tests look like, where they live, and how to run all of them and a single one.
- `docs/conventions/deployment.md`: the environments and their order, how a release is made (pipeline or manual), who approves each environment, the pre-flight list, the post-deploy checks, and the rollback. `/deploy` depends on it.
- `docs/conventions/operations.md`: what is monitored and where logs and metrics live, what normal looks like and the thresholds that matter, the severity tiers, who owns triage, and what may be read or changed in a live system. `/maintain` depends on it.
- `docs/conventions/<other>.md`: any further topic the profile covers, such as language, branching or CI.
- `docs/decisions/NNNN-<slug>.md`: a short decision record (context, decision, alternatives considered, consequences including trade-offs) for each significant choice, so it is not reversed without knowing why.
- `CLAUDE.md`: create it, or add to it if it exists. Import the conventions with `@docs/conventions/<file>.md` and list the build, lint and test commands. Keep it short and do not duplicate the conventions.

## Rules

- Do not mention a specific project in this skill or in the profiles. Project detail belongs in the project's own files.
- When a convention names an architecture, name the pattern (so it can be looked up) and state what each part is responsible for, not only how the parts reference each other.
- Record decisions as plain statements others can follow or check. Prefer wording that a test or hook could later enforce.
- Do not create labels, forms, projects or other GitHub setup here.
Files in this package (4)
  • README.md 3 KB
  • SKILL.md 4 KB
  • profiles/dotnet.md 6 KB
  • profiles/infra.md 7 KB

Versions

RepositoryScoreLicence
This page · carlpaton/skills90MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 754eafecd958 (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

  • 90rules
    AI-First SDLC compliance rules and standards. Use when checking code quality, validating architecture, enforcing zero technical debt, or making any compliance decision.
  • 95sdlc-conventions
    Shared rules for the sdlc-loop plugin - work-folder layout, status.json, file chain (intent -> spec -> plan -> code -> test-report -> deploy-log), human gates, and the per-repo config file `.claude/sdlc-loop.json` (Jira, Figma, Vercel, Supabase ids and app layout). Load this…
  • 100setup-ci
    Generate a GitHub Actions workflow for SDLC validation. Use when setting up CI/CD for a new project.
  • 100sdlc-project-research
    仅在用户明确要求基于仓库证据生成项目功能能力地图、能力盘点或持久研究包时使用;不要用于普通代码探索、repo onboarding、Git 历史问答或只读解释。
  • 100sdlc-navigator
    Provides guidance on which agent to use next and how artifacts connect across SDLC phases. Use when asked about workflow, next steps, which agent to use, or how phases connect.
  • 91new-repository
    New repository bootstrap workflow. Use when creating a new project repository from scratch, setting up all the foundational tooling, CI/CD, and team conventions.

Feedback and reports

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