Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

pipeline-tasks

Sterne1

Forks0

Aktualisiert1. Juli 2026 um 13:56

Use after a delivery plan exists to write thin per-task implementation contracts and complete tasks.yaml for execution.

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

thorrester

thorrester/agent-pipeline-skills

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	pipeline-tasks
description	Use after a delivery plan exists to write thin per-task implementation contracts and complete tasks.yaml for execution.

Pipeline Tasks

Stage 3: plan -> executable tasks.

Turn a plan DAG into one thin task contract per node: .pipeline/<feature>/tasks/NN-<slug>.md.

Process

Read spec.md, plan.md, and the target repo context.
For each plan node, identify source anchors: symbols, files, commands, tests, contracts, or docs the implementer must respect.
Write a thin task contract. Do not include full function bodies, generated SQL, or long code sketches.
Update tasks.yaml so every node has areas, anchors, verify, and status: pending.

Task Contract Shape

# Task NN: <Title>

## Goal

## Inputs
- Spec:
- Plan:

## Anchors And Invariants
- <symbol/file/command/contract> MUST ...

## Expected Changes

## Verify
- <command>

## Acceptance
- <observable result>

Handoff

tasks.yaml + tasks/ -> pipeline-implement.

Mehr aus diesem Repository

gleiches Repository

pipeline-finalize

thorrester/agent-pipeline-skills

Use after review-and-plan to verify the full pipeline ran, implementation aligns with the spec, final gates pass, and human plus agent journey coverage exists.

2026-07-011

pipeline-implement

thorrester/agent-pipeline-skills

Use after tasks.yaml and thin task contracts exist to implement the dependency-ordered task graph and mark tasks done only after verification passes.

2026-07-011

pipeline-plan

thorrester/agent-pipeline-skills

Use after an approved spec to create a dependency-ordered software delivery plan and tasks.yaml skeleton before task contracts or implementation.

2026-07-011

pipeline-review-and-plan

thorrester/agent-pipeline-skills

Use after implementation to run a full generic code review, validate findings, and write a prioritized implementation plan for confirmed fixes.

2026-07-011

pipeline-spec

thorrester/agent-pipeline-skills

Use when turning a raw software feature idea into an approved specification before planning, tasks, implementation, review, or finalization.

2026-07-011

pipeline-validate-reviews

thorrester/agent-pipeline-skills

Use after pipeline-review-and-plan reviewer reports exist to eliminate false positives and write a prioritized implementation plan from confirmed findings.

2026-07-011

name	pipeline-tasks
description	Use after a delivery plan exists to write thin per-task implementation contracts and complete tasks.yaml for execution.

Pipeline Tasks

Stage 3: plan -> executable tasks.

Turn a plan DAG into one thin task contract per node: .pipeline/<feature>/tasks/NN-<slug>.md.

Process

Read spec.md, plan.md, and the target repo context.
For each plan node, identify source anchors: symbols, files, commands, tests, contracts, or docs the implementer must respect.
Write a thin task contract. Do not include full function bodies, generated SQL, or long code sketches.
Update tasks.yaml so every node has areas, anchors, verify, and status: pending.

Task Contract Shape

# Task NN: <Title>

## Goal

## Inputs
- Spec:
- Plan:

## Anchors And Invariants
- <symbol/file/command/contract> MUST ...

## Expected Changes

## Verify
- <command>

## Acceptance
- <observable result>

Handoff

tasks.yaml + tasks/ -> pipeline-implement.