architect

Use this skill at two distinct moments in a VADER project. (Mode = draft) When a vision doc exists and an initial architecture doc is needed before drafting the wave plan. Triggers include phrases like "draft the architecture for this project", "produce an architecture doc and Decision Log from this vision", "design the modules and key interfaces for X", or whenever the user wants the structural decisions for a new project committed to writing before wave planning starts. (Mode = ratify) After the user has reviewed the proposed architecture and decisions, to flip Proposed Decision Log entries to Accepted in one pass. Trigger when the user says "ratify the architecture" or "accept the proposed decisions". Do NOT use for mid-cycle architectural revision — that's handled by `wave-update`'s review subagent. Do NOT use to produce code, scaffolding, or implementation; this skill produces decision documents only.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "architect" with this command: npx skills add vtphan/skillsmp-vtphan-vtphan-architect

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Coding

design

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.

Repository SourceNeeds Review

-0vtphan

Coding

execute

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.

Repository SourceNeeds Review

-0vtphan

Coding

intent

Use this ACCORD skill when the human lead wants to codesign or revise project intent before architecture/design work. Triggers include "accord intent", "draft project intent", "revise intent", "pivot intent", or when a project needs a lightweight approved intent artifact for downstream design and planning. This skill uses monotonic draft rounds, promotes an approved draft to docs/accord/intent/intent.md, updates accord-state.md, then commits and tags after human approval.

Repository SourceNeeds Review

-0vtphan

Coding

wave-plan

Use this skill when a vision doc and a ratified architecture doc exist, and the user wants the initial wave plan drafted. Triggers include phrases like "draft the wave plan from the vision and architecture", "produce the initial wave plan for this project", "what's W1 for this project", "break this into waves with W1 as a walking skeleton", or whenever the upstream vision and architecture artifacts are ready and the next step is committing them into a rolling-wave plan. Do NOT use when no architecture doc exists yet (run `architect draft` first). Do NOT use to revise an existing wave plan — that's `wave-update`. Do NOT use to write code; this skill produces a planning document only.

Repository SourceNeeds Review

-0vtphan