pvtvv
Community@pvtvv
pvtvv provides OpenSpec change-management skills for proposing, implementing, updating, syncing, and archiving specification-driven software changes.
Agent Skills by pvtvv
Showing 6 vetted skills indexed across 1 GitHub repositories.
pvtvvopenspec-apply-change
Implements tasks from an OpenSpec change using the openspec CLI workflow.
pvtvvopenspec-explore
Explores ideas and investigates codebases as a thinking partner before creating OpenSpec change proposals.
pvtvvopenspec-update-change
Revise OpenSpec change planning artifacts and keep them coherent with each other.
pvtvvopenspec-archive-change
Archives completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.
pvtvvopenspec-propose
Generates complete OpenSpec change proposals with specs, design, and tasks artifacts.
pvtvvopenspec-sync-specs
Merge delta spec changes into main OpenSpec capability specifications.
Frequently Asked Questions About pvtvv
FAQPage SchemaWhat tasks can I perform using pvtvv's OpenSpec skills?▼
You can propose new changes with full design, spec, and task artifacts, explore ideas and clarify requirements, implement change tasks, revise existing planning artifacts, sync delta specs into main specs, and archive completed changes.
Who are these OpenSpec skills designed for?▼
They target software engineers and technical leads practicing specification-driven development who need structured change proposals, coherent planning artifacts, and a disciplined lifecycle from proposal through implementation to archival.
What is required to run these skills?▼
Each skill requires the openspec CLI to be installed, as declared in the compatibility field. All skills invoke Bash commands scoped to openspec, so a working openspec installation in the environment is the only stated prerequisite.
Are pvtvv's OpenSpec skills free to use?▼
Yes. All six skills are released under the MIT license, permitting free use, modification, and distribution. They are authored by openspec at version 1.0, generated by version 1.10.0.
How do the skills work together across a change lifecycle?▼
Start with openspec-propose or openspec-explore to define the change, implement tasks with openspec-apply-change, revise plans with openspec-update-change, then either sync delta specs via openspec-sync-specs or finalize with openspec-archive-change.