Use this ACCORD skill after execute has produced an execution report and the human lead wants the work reviewed and the plan updated. Triggers include "accord review-update", "review the executed unit", "update the plan after execution", "close this unit", or "what comes next after execute". This skill verifies execution, writes review/update entries into docs/accord/plan/plan.md by default, updates accord-state.md, then commits and tags after human approval.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "review-update" with this command: npx skills add vtphan/skillsmp-vtphan-vtphan-review-update
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Use this ACCORD skill when approved intent and design artifacts exist and the human lead wants an adaptive implementation plan or a revised plan. Triggers include "accord plan", "draft the plan", "choose the next unit", "revise the plan", or when planning needs to adapt after review. The skill may use monotonic draft rounds, promotes an approved draft to docs/accord/plan/plan.md, updates accord-state.md, then commits and tags after human approval.
Use this skill at two distinct moments in a VADER project. (Mode = draft) When the user has a rough idea for a software product or system and wants help shaping it into a vision document. Triggers include phrases like "I have an idea for X, help me think it through", "shape this into a vision doc", "draft a vision for this", "let's brainstorm this product idea", or whenever the user describes an idea conversationally and asks for help making it concrete enough to plan against. (Mode = pivot) When an existing vision doc needs revision because something learned during execution has invalidated a core part of it. Triggers include phrases like "the vision needs to change because of W3", "we need to pivot — the value hypothesis didn't hold", "update the vision to reflect <core change>", or whenever the user explicitly says "vision pivot". Do NOT use to draft requirements, stories, or features (those live in the wave plan). Do NOT use for cosmetic edits or clarifications that don't change the project's direction (t
Use this ACCORD skill when an approved intent exists and the human lead wants to codesign or revise architecture, boundaries, project commands, verification expectations, and consequential decisions. Triggers include "accord design", "draft the design", "revise architecture", "pivot design", or when implementation learning requires a new design version. This skill uses monotonic draft rounds, promotes an approved draft to docs/accord/design/design.md, updates accord-state.md, then commits and tags after human approval.
Use this ACCORD skill when canonical intent, design, and plan artifacts exist and the human lead wants the current approved unit implemented. Triggers include "accord execute", "execute the current unit", "implement the approved unit", "build the next unit", or "go ahead" after an approved ACCORD plan. This skill writes code, writes docs/accord/reports/exec-<unit-id>.md using the approved u-NNN-slug ID, updates accord-state.md, then commits and tags after human approval.