Skip to content

moonlight-lupin/agent-skills / plugins/dev-pipeline/skills/spec

Use when pinning intent before code — capture a spec (user stories, acceptance criteria, [NEEDS CLARIFICATION] markers), then plan the HOW (bite-sized tasks, blocking edges, gates) or slice tracer-bullet tickets. Triggers: 'write a spec', 'plan this', 'break this into tickets', 'slice this up', 'create tickets', 'what are the work units'.

references/goldfish/standards/re-implementation-standard.md

View on GitHub
# Re-Implementation Standard

This standard defines the quality bar for documenting codebase state.

## Core Principle

A document passes if a competent engineer (or fresh AI session) who is
unfamiliar with the codebase can write functionally identical code on the first
attempt using *only* the document, without guessing or making independent design
choices.

## The Zero-Assumption Rule

The document fails if the reader must guess parameter defaults, assume error
handling, choose design patterns, or infer output schemas. Every behaviorally
significant contract must be explicit.

## Scope of Detail

*   **Include**: External contracts (APIs, formats, side-effects), behavioral
    rules (logic, state, errors), and performance constraints.
*   **Exclude**: Syntax (loops, variable names), internal code organization
    (private helpers), and non-observable structures (internal collections).

## Requirements (Non-Exhaustive Examples)

Document these areas if applicable to the codebase scope:

*   **APIs**: Signatures, types, and expected behavior.
*   **Logic**: Control flow, algorithms, and validation.
*   **Data**: Schemas, serialization, and state transitions.
*   **Side Effects**: Database writes, network calls, logging, and metrics.
*   **Dependencies**: System integrations and libraries.
*   **Configuration**: Flags, parameters, and hooks.
*   **Constraints**: Hardcoded limits and assumptions.
*   **Errors**: Edge cases, empty states, and retries.
*   **Tests**: Test helpers and mocks (if documenting tests).
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall