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/implementation-readiness-standard.md

View on GitHub
# Implementation Readiness Standard

This standard defines the quality bar for implementation plans and task lists.

## Core Principle

A plan passes if a competent engineer (or fresh AI session) who is unfamiliar
with the codebase can execute the plan and produce the correct changes on the
first attempt, without guessing, asking clarifying questions, or making
independent design choices.

## The Zero-Decision Rule

The plan must leave **zero design or architectural choices to the implementer**.
If the implementer must make design choices (including, but not limited to,
choosing a database schema, designing an API path, selecting a dependency, or
deciding how to handle a new edge case), the plan **fails** this standard. All
such decisions must be pre-determined and documented in the plan.

## Phasing & Checkpoints

The plan must partition the work into logical, incremental phases. Each phase
must leave the codebase in a stable, buildable, and testable state.

## Requirements (Non-Exhaustive Examples)

The plan must detail these areas if applicable to the proposed changes:

*   **Target Scope**: Explicit list of files to be created, modified, or
    deleted.
*   **Actionable Steps**: Precise logic changes, data transformations, and API
    updates for each file.
*   **Test Plan**: Specific test cases (happy path and edge cases) that must be
    implemented.
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