specs-overview

Included with Lifetime

$97 forever

Generate or regenerate specs/OVERVIEW.md with a tabular summary, status, and per-spec file listings

General

What this skill does


# Specs Overview Generator

Generate a `specs/OVERVIEW.md` file that catalogues all feature specs in the project's `specs/` directory. This skill can create the file from scratch or fully regenerate it.

## Prerequisites

- A `specs/` directory must exist in the project root
- At least one spec subdirectory must exist with spec files (requirements.md, smolspec.md, design.md, plan.md, etc.)

## Process

### 1. Discover Specs

- List all subdirectories under `specs/`
- Exclude `specs/bugfixes/` (bug-specific specs are tracked separately)
- For each directory, collect:
  - **Directory name** (used as the spec identifier)
  - **Display name** (derived from directory name: kebab-case to Title Case)
  - **Creation date** (earliest git commit that added files in the directory): `git log --diff-filter=A --format='%aI' -- 'specs/{dirname}/'` — take the last (oldest) entry, format as YYYY-MM-DD
  - **Status** — determined by examining the spec's task file:
    - `Done` — all tasks are completed (all checkboxes checked)
    - `In Progress` — some tasks are completed, some remain
    - `Planned` — tasks exist but none are completed
    - `No Tasks` — no tasks.md file exists
  - **Summary** — a one-sentence description (max ~15 words) extracted from the first substantive paragraph of the primary document (check in order: requirements.md, smolspec.md, design.md, plan.md, implementation.md)
  - **Files** — list of all `.md` files in the directory (exclude non-documentation artifacts like `comparison-report` directories)

### 2. Generate the Overview

The output file `specs/OVERVIEW.md` MUST follow this structure:

```markdown
# Specs Overview

| Name | Creation Date | Status | Summary |
|------|---------------|--------|---------|
| [Spec Name](#anchor) | YYYY-MM-DD | Status | One-line summary |
...

---

## Spec Name

One-line summary.

- [filename.md](spec-dir/filename.md)
- [filename2.md](spec-dir/filename2.md)
...
```

**Table rules:**
- Sort rows chronologically by creation date (oldest first)
- Name column links to the detail section anchor below the table (e.g., `[Spec Name](#spec-name)`)
- Anchors are the display name lowercased with spaces replaced by hyphens

**Detail section rules:**
- One H2 section per spec, in the same chronological order as the table
- Summary line repeated below the heading
- Bulleted list of all `.md` files in the spec directory, each linking to the file relative to `specs/`
- Exclude non-markdown items (directories like `comparison-report`, `.DS_Store`, etc.)

### 3. Write the File

- Write the complete file to `specs/OVERVIEW.md`
- If the file already exists, overwrite it entirely (this is a full regeneration)

## Constraints

- The model MUST NOT include specs from `specs/bugfixes/`
- The model MUST use git history for creation dates, not filesystem timestamps
- The model MUST examine task files to determine status, not guess from other signals
- The model SHOULD parallelize git date lookups and file reads where possible for efficiency
- The model MUST NOT create any files other than `specs/OVERVIEW.md`

Files: 1

Size: 3.2 KB

Complexity: 6/100

Category: General

Source: https://github.com/arjenschwarz/agentic-coding/tree/main/claude/skills/specs-overview

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