Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

pm-report

Sterne0

Forks0

Aktualisiert1. Mai 2026 um 23:30

Append a TaskReport (proof of work / progress note) to a task. Reports are immutable and chained: each new report links prevReport to the previous one. A report is required before pm:finished will accept the task. Use when an agent finishes its work and produces output, or when capturing partial progress mid-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

in8finity

in8finity/hashharness-pm

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

ProjektmanagementspezialistenWirtschafts- und Finanzberufe·SOC 13-1082

SKILL.md

readonly

name	pm-report
description	Append a TaskReport (proof of work / progress note) to a task. Reports are immutable and chained: each new report links prevReport to the previous one. A report is required before pm:finished will accept the task. Use when an agent finishes its work and produces output, or when capturing partial progress mid-execution.

pm:report — submit a report on a task

Procedure

../scripts/pm report --task <task-sha> --title "..." \
    (--text "..." | --text-file path/to/report.md)

Appends a TaskReport with links.task = <task-sha> and links.prevReport = <previous-report-sha> (omitted on the first report).
The report body is the proof of work: include outputs, file paths, diffs, test results — whatever evidence justifies completion.
Multiple reports per task are allowed (e.g. interim updates). The last report is the one that pm:finished will reference as proof.

Mehr aus diesem Repository

gleiches Repository

pm-execute

in8finity/hashharness-pm

Run N worker agents in parallel that drain the planning queue. Each worker loops: pull next task -> claim it (executing) -> do the work -> submit a report -> finish the task. Use when the user says "execute the plan", "run the queue", "spawn workers", or asks for parallel execution with a specific agent count.

2026-05-300

in8finity/hashharness-pm

Planning-board skill bundle for coordinating parallel coding agents with hashharness-backed append-only task, status, and report chains. Use this as the entry point to the bundled pm subskills under this directory, such as `plan`, `next`, `executing`, `report`, `finished`, `execute`, `replan`, `cancel`, `reclaim`, `sweep`, `dashboard`, `install`, `extract-steps`, and the `*-skill-execution` variants.

2026-05-300

pm-audit

in8finity/hashharness-pm

Cryptographic integrity attestation of a planning queue or the whole pm instance via hashharness `verify_work_package`. Re-checks every record's content hash, chain links, and schema binding across the queue's Task records plus each per-task TaskStatus / TaskReport / TaskHeartbeat chain — catching orphan records, tampered payloads, and `done` slipped in without proof. Unlike `verify_chain` (which followed a single named root), this covers every record in scope, closing the gap that pm's per-task chains have no common root. Use as a supervisor sweep before trusting a batch of agent output, or as a periodic integrity check.

2026-05-290

pm-plan

in8finity/hashharness-pm

Enqueue a new task on the planning board backed by hashharness. Creates an immutable Task record plus an initial TaskStatus(new). Supports subtasks (link to parent + parent's status at decision point) and dependency links to other tasks. Use when the user says "plan", "queue", "enqueue", "add task", or "create subtask".

2026-05-290

pm-install

in8finity/hashharness-pm

Install the hashharness MCP backend that pm uses for its append-only storage. Bootstraps an isolated Python venv, installs hashharness from git, generates a launcher script and a source-able env file. Four install locations: ~/.hashharness/ (per-user, recommended), ~/.codex/hashharness/ (alongside Codex state), ~/.claude/hashharness/ (alongside Claude Code skills), or ./.hashharness/ (per-project at git root). Idempotent — re-running reports the existing install and exits 0. Use when a fresh workstation needs hashharness, when "pm setup" fails because no MCP server is reachable, or when you want a sandboxed second instance for testing.

2026-05-230

pm-extract-steps

in8finity/hashharness-pm

Extract the major workflow steps from another skill's SKILL.md, with bash-side validation that every extracted step's anchor is verbatim in the source (catches LLM hallucination), and optional recursion into nested skill invocations (step X of skill A invoking skill B yields nested steps named `X.B.S1`, `X.B.S2`, ...). Two modes — llm (semantic, default when a supported LLM CLI is on PATH) and regex (pattern- matching fallback). Used internally by pm-auto-skill-execution, pm-assisted-skill-execution, pm-guided-skill-execution; also callable standalone for inspecting a skill's structure.

2026-05-150

name	pm-report
description	Append a TaskReport (proof of work / progress note) to a task. Reports are immutable and chained: each new report links prevReport to the previous one. A report is required before pm:finished will accept the task. Use when an agent finishes its work and produces output, or when capturing partial progress mid-execution.

pm:report — submit a report on a task

Procedure

../scripts/pm report --task <task-sha> --title "..." \
    (--text "..." | --text-file path/to/report.md)

Appends a TaskReport with links.task = <task-sha> and links.prevReport = <previous-report-sha> (omitted on the first report).
The report body is the proof of work: include outputs, file paths, diffs, test results — whatever evidence justifies completion.
Multiple reports per task are allowed (e.g. interim updates). The last report is the one that pm:finished will reference as proof.