How does Architect handle missing information?

It classifies missing data as blocking, derivable, or deferrable. Blocking issues are routed back to the user or discovery tools like brainstorm before any plan is written.

When should I use the Architect skill instead of direct execution?

Use Architect for complex, multi-step, or high-risk requests where implementation boundaries, contracts, or UI directions are still ambiguous.

Does this skill support localized planning?

Yes, the skill is configured to generate controller-facing plan artifacts in plain Korean, ensuring clear visibility for specific regional project requirements.

What is the role of the review wiki in this skill?

The review wiki serves as a registry for core documents and patterns, providing the Architect with mandatory routing contracts and technical guidance specific to your repository.

Implementation Architect

Name: Implementation Architect
Author: SeoJaeWan

bySeoJaeWan

0•

Productividad y Flujo de Trabajo

Generates decision-complete, traceable implementation plans and executable phase artifacts for complex coding tasks.

The Architect skill acts as a bridge between high-level discovery and hands-on execution by transforming abstract requests into concrete, sequential implementation plans. It specializes in resolving blocking ambiguities across UX, schema, and policy before work begins, ensuring that every step is traceable and decision-complete. By utilizing a registry-backed review wiki and standardizing plan artifacts in a dedicated directory, it provides a structured framework for both direct and orchestrated agent workflows, eliminating guesswork during the development lifecycle.

Características Principales

01Sequential executable planning with traceable phase artifacts

020 GitHub stars

03Registry-backed review wiki for pattern-consistent guidance

04Integration with Context7 for real-time external API and library verification

05Automated resolution of blocking technical and product ambiguities

06Scenario-first boundary definition and public I/O contract mapping

Casos de Uso

01Standardizing repository-local conventions through a centralized review wiki and planning registry

02Drafting multi-phase technical roadmaps for high-impact feature implementations

03Resolving UI/UX and API contract ambiguity before starting the coding process

Características Principales

01Sequential executable planning with traceable phase artifacts

020 GitHub stars

03Registry-backed review wiki for pattern-consistent guidance

04Integration with Context7 for real-time external API and library verification

05Automated resolution of blocking technical and product ambiguities

06Scenario-first boundary definition and public I/O contract mapping

Casos de Uso

01Standardizing repository-local conventions through a centralized review wiki and planning registry

02Drafting multi-phase technical roadmaps for high-impact feature implementations

03Resolving UI/UX and API contract ambiguity before starting the coding process