constitution

Included with Lifetime

$97 forever

Use when the user invokes $spec-kit:constitution or /spec-kit:constitution, or asks to generate or update a pragmatic solo-dev project constitution.

General

What this skill does

# Spec Kit Constitution

This is a user-invoked Spec Kit workflow. Treat user text after the invocation as the workflow input.

## Plugin Root

Use the spec-kit plugin root when running bundled scripts. In Claude Code, `${CLAUDE_PLUGIN_ROOT}` resolves to this plugin root. If that variable is unavailable, resolve the plugin root as the directory two levels above this `SKILL.md`.

User input:

$ARGUMENTS

Create or update `.specify/memory/constitution.md`. The constitution is a small
set of guardrails for future specs, plans, and tasks. For this plugin, it must
be useful to a solo indie developer working in existing repos, not a ceremonial
process document.

## Preflight

1. Ensure `.specify/memory/` exists.
2. Run the context detector if available:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/detect-project-context.sh" --write
```
3. Read project context, README, AGENTS.md, package/tooling files, and any
existing constitution.

## Constitution Style

Generate 4-7 principles. Prefer these themes unless project context demands
otherwise:
- Existing architecture first
- Small, reviewable changes
- Risk-proportional testing and verification
- Clear contracts for data, APIs, jobs, CLI, or UI behavior
- Safety around migrations, credentials, external services, and destructive
operations
- Documentation/context updates only when they reduce future prompting

## Required Waiver Language

Include a governance rule like:

"Documented waivers are allowed for solo-dev pragmatism. A waiver must name the
principle, explain why the simpler compliant option is worse for this change,
and record the compensating validation in `plan.md`."

This keeps the constitution authoritative without forcing upstream Spec Kit's
library-first, CLI-first, or strict TDD rules onto every brownfield repo.

## Output Structure

Write:

```markdown
# [Project Name] Constitution

## Core Principles

### I. [Principle]
[Concrete MUST/SHOULD rules and brief rationale]

### II. [Principle]
...

## Brownfield Workflow
[Rules for fitting existing repos]

## Quality Gates
[How plans/tasks prove compliance]

## Governance
[Versioning, amendment, waiver, and review rules]

**Version**: [X.Y.Z] | **Ratified**: [YYYY-MM-DD] | **Last Amended**: [YYYY-MM-DD]
```

## Versioning

- Initial real constitution: `1.0.0`
- MAJOR: principle removed or fundamentally redefined
- MINOR: principle or required gate added
- PATCH: clarification, wording, or non-semantic tightening

## Sync Impact

Do not update every template like upstream Spec Kit. Instead, report the
affected gates/artifacts:
- `plan.md` constitution compliance
- `tasks.md` quality gates
- `.specify/memory/project-context.md`
- Any repo guidance file such as `AGENTS.md`, only if the user asks

## Report

Report:
- Version and bump rationale
- Principle list with one-line summaries
- Any deferred TODOs
- Suggested commit message
- Next workflow step: `/spec-kit:specify <feature description>`

Files: 2

Size: 3.3 KB

Complexity: 13/100

Category: General

Source: https://github.com/grailautomation/claude-plugins/tree/main/spec-kit/skills/constitution

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts