PHMbench
Official@phmbench
Offers structured documentation, experiment configuration, and task orchestration for managing technical project lifecycles through standardized Markdown and JSON manifests.
Agent Skills by PHMbench
Showing 8 vetted skills indexed across 1 GitHub repositories.
config-manager-skill
Automate PHM-Vibench experiment configuration with recursive merging and validation.
vibe-batch-orchestrator
Coordinate backlog items into a triage-to-sprint workflow with optional documentation outputs.
plan-md-executor
Convert plan_<topic>.md files into structured exec_<topic>.md execution sequences.
plan-md-writer
Parse intake_<topic>.md and generate plan_<topic>.md with standard Plan attributes.
artifact-manifest-writer
Aggregate execution changes, commands, verifications, and deliverables into a structured JSON manifest.
daily-vibe-update
Generate daily.md and todo.md reports from a plan and date.
intake-normalizer
Convert scattered notes, logs, ideas, and issues into structured Intake Markdown files.
workflow-to-skill
Convert manual workflows into structured SOP maps and SKILL.md drafts.
Frequently Asked Questions About PHMbench
FAQPage SchemaWhat specific tasks does PHMbench enable for project teams?▼
PHMbench enables the normalization of scattered project notes into structured Markdown, the conversion of planning documents into execution sequences, and the aggregation of project deliverables into JSON manifests. It facilitates consistent experiment configuration and the transformation of manual processes into standardized SOP maps.
Which personas benefit most from using these project management capabilities?▼
Technical project managers, systems engineers, and operations leads benefit from these capabilities. The system is designed for professionals who require rigorous documentation standards, structured task triage, and the ability to track experiment configurations and execution changes across complex project lifecycles.
What are the prerequisites for implementing PHMbench in a project environment?▼
Implementation requires a project environment centered on Markdown-based documentation and structured file naming conventions. Users must maintain intake files, plan documents, and execution logs in a compatible directory structure to allow the system to parse, normalize, and aggregate data into the required JSON manifest outputs.