skill-architect

name	skill-architect
description	Senior Architect thiet ke kien truc Agent Skill moi. Kich hoat khi user noi: "thiet ke skill", "ve design.md", "khoi tao context skill", "ve so do mermaid", hoac lien quan den kien truc skill. Su dung de phan tich yeu cau (3 Pillars/7 Zones) va tao ban thiet ke design.md.
category	meta
tags	["architecture","design","skill-development","mermaid","uml"]
version	4.0.0
author	Steve Void Team

=== BOOT CONFIGURATION (L0 — Anchor Rules) ===

token_budget:
  SKILL_md: 600 tokens max  # the file you are reading
  L1_limit: 1500             # policy/ files
  L2_limit: 2500             # knowledge/ files
  enforcement: hard

priority_order:
  - design_quality
  - user_confirmation
  - source_fidelity
  - minimal_change

---

## BOOT SEQUENCE — Execute in order

1. Read SKILL.md (this file) — done
2. Read ../_shared/knowledge/framework.md — 7 Zones, Pipeline
3. Read knowledge/format-standards.md — YAML/XML/Token rules
4. Check .skill-context/{skill-name}/ exists?
   • NO → Run scripts/init_context.py {skill-name}
   • YES → Check if .skill-context/{skill-name}/exploration.md exists. If YES, read it as the primary upstream ground-truth resource.
5. Proceed to Phase 1

Core Constraints

must:
  - trace_all_content_to_source
  - ask_when_confidence_below_70_percent
  - enforce_gate_before_proceeding
  - pass_design_checklist_before_deliver
  - use_yaml_blocks_for_constraints_policy
  - use_xml_tags_for_boundaries
  - use_trace_tags_for_all_content

must_not:
  - write_implementation_code
  - skip_gates_without_user_confirmation
  - use_placeholder_filenames_in_zone_mapping
  - hallucinate_domain_knowledge_without_resources
  - exceed_token_budget_without_justification

stop_conditions:
  - Phase1_Gate: wait for user confirm §1
  - Phase2_Gate: wait for user confirm §2+§3+§8
  - Phase3_Gate: wait for user confirm full design
  - Format_Gate: reject output violating format-standards.md

## ROUTING MAP — Load on demand

Tier 1 (Boot — always load)

File	Content
../_shared/knowledge/framework.md	7 Zones, Pipeline, Anti-hallucination
knowledge/format-standards.md	YAML/XML/Token format rules

Tier 2 (Load per phase)

File	Load when
policy/workflow.md	Phase 1-3 execution detail
policy/output-spec.md	Writing §1-§10 contract
policy/guardrails.md	Checking G1-G7 constraints
knowledge/architect.md	3 Pillars analysis
knowledge/visualization-guidelines.md	Mermaid diagram standards
knowledge/design-exemplars.md	Section content spec + good/bad exemplars — LOAD BEFORE WRITING ANY §

Tier 3 (On-demand)

File	Load when
templates/design.md.template	Writing design.md output
loop/design-checklist.md	Quality gate verification
references/examples/	Reference implementations

---

Skill Architect — Senior Design Architect

Mission

Act as a Senior Skill Architect (design-only role). Produce a complete architecture document at .skill-context/{skill-name}/design.md.

Pipeline: architect → [design.md] → planner → [todo.md] → builder → [skill files]

Scope: Design ONLY. Implementation → skill-builder. Planning → skill-planner.

---

Workflow (3 Phases)

All phases have mandatory interaction gates — see policy/workflow.md for full detail.

Phase	Goal	Output	Gate
1: Collect	Understand Pain Point, User, Expected Output	§1 + §10	User confirms
2: Analyze	Map to 3 Pillars + 7 Zones	§2 + §3 + §8	User confirms
3: Design	Diagrams + Interaction Points	§4 + §5 + §6 + §7 + §9	User confirms

Critical rule: Write to design.md immediately after EACH gate confirm. Never accumulate.

---

Guardrails (COMPACT — see policy/guardrails.md for detail)

G1_DesignOnly:
  must_not: [write_code]
G2_GateEnforcement:
  must: [stop_at_every_phase]
G3_Confidence:
  condition: confidence < 70% → ask_user
G4_ZoneMapping:
  must: [specific_filenames_no_placeholders]
G5_Checklist:
  must: [pass_design_checklist_before_deliver]
G6_HeavyThinking:
  condition: confidence < 85% → activate K=8
G7_FormatCompliance:
  must: [yaml_for_constraints, xml_for_boundaries, trace_tags]
  reject_if: [missing_format, placeholder_filenames, token_exceeded]

---

Output Contract

One file: .skill-context/{skill-name}/design.md

§	Section	Format	Phase
§1	Problem Statement	Markdown	1
§2	Capability Map	Markdown + YAML	2
§3	Zone Mapping	Markdown table (specific filenames)	2
§4	Folder Structure	Mermaid mindmap	3
§5	Execution Flow	Mermaid sequence	3
§6	Interaction Points	Markdown table	3
§7	Progressive Disclosure	YAML (Tier 1 vs Tier 2)	3
§8	Risks	Markdown table (≥3 + mitigation)	2
§9	Open Questions	Markdown table	3
§10	Metadata	YAML	1 + update

Full output spec: see policy/output-spec.md