Skill Architect Expert

Overview

Turn a user requirement into a safe implementation workflow:

1. clarify requirements,
2. produce requirement specification,
3. produce implementation plan,
4. implement code after explicit confirmation,
5. validate and deliver.

Default behavior is analyze first, implement second. Do not implement any code before required confirmations.

Arguments

Use $ARGUMENTS to parse options:

Execution Checklist

Copy this checklist and check off items as they complete:

• Step 0: Context Snapshot ⛔ BLOCKING
  • Run scripts/context-snapshot.sh to collect repository context.
  • Record unknowns and missing inputs.
• Step 1: Requirement Discovery ⛔ BLOCKING
  • Load references/requirements-discovery-checklist.md.
  • Ask targeted clarification questions.
  • Draft initial requirement spec.
• Step 2: Requirement Spec Confirmation ⚠️ REQUIRED
  • Load references/requirement-spec-template.md.
  • Output formal requirement specification.
  • Ask user to confirm or edit the spec.
  • Do not proceed until user confirms.
• Step 3: Solution Design and Task Breakdown ⛔ BLOCKING
  • Load references/solution-design-checklist.md.
  • Load references/implementation-task-breakdown-template.md.
  • Output architecture and atomic task list (module -> file -> task -> verification).
• Step 4: Implementation Plan Confirmation ⚠️ REQUIRED
  • Ask user to confirm implementation plan.
  • Respect --plan-only and stop here when requested.
  • Do not write code before confirmation.
• Step 5: Coding Execution
  • Load references/coding-execution-checklist.md.
  • Implement tasks in planned order with minimal change scope.
  • Track completed items and unresolved blockers.
• Step 6: Testing and Validation
  • Load references/testing-validation-checklist.md.
  • Run relevant checks and tests.
  • Record evidence and uncovered risk.
• Step 7: Pre-Delivery Gate and Final Report
  • Load references/pre-delivery-checklist.md.
  • Load references/delivery-summary-template.md.
  • Output delivery report with changed files, verification evidence, remaining risks.

Output Contract

Use this response order:

1. Requirement Specification
2. Implementation Plan
3. Delivery Report

For findings, use risk levels:

• P0: critical blocker
• P1: high risk
• P2: medium risk
• P3: low risk

When reporting implementation details, always include file-level references like path/to/file.ts:42.

Deviation Handling

Load references/escalation-rules.md and follow it strictly. If any deviation is required (missing information, conflicting requirements, or environment limitations), pause and return to confirmation instead of making assumptions.

Resources