Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

speckit-checklist

Sterne456

Forks19

Aktualisiert29. März 2026 um 17:06

Use when working in this Spec Kit repository and the user wants a requirements-quality checklist for the active feature, generated from the current spec, plan, and tasks artifacts.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

zolotukhin

zolotukhin/zinc

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	speckit-checklist
description	Use when working in this Spec Kit repository and the user wants a requirements-quality checklist for the active feature, generated from the current spec, plan, and tasks artifacts.

Speckit Checklist

Use this skill for the Spec Kit checklist phase.

Read ../../../.claude/commands/speckit.checklist.md and treat it as the authoritative workflow.
Treat the current user request as the $ARGUMENTS referenced there.
Translate slash-command references to Codex skill names such as speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues.
Use the repo-local .specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.
Preserve the checklist intent from the source workflow: validate the quality of written requirements, not implementation behavior.
Do not create Codex custom prompt files. Codex support in this repo is skill-based.

Mehr aus diesem Repository

gleiches Repository

zig-docgen

zolotukhin/zinc

Use when adding or editing Zig code in ZINC and you want it to remain compatible with the auto-generated Zig API docs. Covers the comment format, supported tags, parser limitations, section naming, and validation steps needed for reliable HTML, JSON, text, and llms exports.

2026-05-25456

speckit-analyze

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants a read-only consistency and coverage analysis across the active feature's spec.md, plan.md, and tasks.md before implementation.

2026-03-29456

speckit-clarify

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to resolve ambiguity in the active feature spec by asking targeted clarification questions and writing the accepted answers back into spec.md.

2026-03-29456

speckit-constitution

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to create or amend the project constitution in .specify/memory/constitution.md and keep dependent templates aligned.

2026-03-29456

speckit-implement

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to execute the active tasks.md plan, respecting checklist gates, task dependencies, and phase-by-phase implementation.

2026-03-29456

speckit-plan

zolotukhin/zinc

Use when working in this Spec Kit repository and the user wants to turn the active feature spec into an implementation plan and design artifacts such as research.md, data-model.md, contracts, and quickstart.md.

2026-03-29456

name	speckit-checklist
description	Use when working in this Spec Kit repository and the user wants a requirements-quality checklist for the active feature, generated from the current spec, plan, and tasks artifacts.

Speckit Checklist

Use this skill for the Spec Kit checklist phase.

Read ../../../.claude/commands/speckit.checklist.md and treat it as the authoritative workflow.
Treat the current user request as the $ARGUMENTS referenced there.
Translate slash-command references to Codex skill names such as speckit-specify, speckit-clarify, speckit-plan, speckit-tasks, speckit-analyze, speckit-implement, speckit-checklist, speckit-constitution, and speckit-taskstoissues.
Use the repo-local .specify/scripts/bash/*.sh and .specify/templates/*.md files the workflow calls for.
Preserve the checklist intent from the source workflow: validate the quality of written requirements, not implementation behavior.
Do not create Codex custom prompt files. Codex support in this repo is skill-based.