Organize complex requests into executable plans with phase-detail files.
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill architect-seojaewan
Please help me install this Agent Skill. Skill: architect Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/.codex/skills/architect Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill architect-seojaewan
Create decision-complete implementation plans as one or more sequential executable plans, with explicit execution phases, scenario-first boundary I/O contracts, and controller-facing plan artifacts that preserve the user's wording, expose concrete work bundles and public contracts before execution order, and keep later execution from guessing.
Describe a complex request and let Architect generate a sequential, executable plan with clearly defined phases and linked phase-detail files under plans.
High-intent search queries and answers about installing and using this skill.
Executable steps for complex requests are organized into a structured plan with defined phases and public contracts. The process generates a plan.md and linked phase-detail files under ./plans/{task-slug}/ to expose concrete work bundles before execution begins.
An artifact-driven plan is a decision-complete implementation strategy that preserves user wording and exposes public contracts before execution. You need it for high-impact tasks requiring multiple plan artifacts, phase-detail files, and registry-backed review guidance.
To create phase-detail files and a plan.md, describe your complex request to generate a sequential, executable plan. The system automatically creates per-phase detail files and a main plan file under the plans directory with YAML frontmatter defining name and description.
Yes, review-wiki contracts align with execution handoff policies to coordinate design, review, and execution phases. The system orchestrates these handoffs using registry-backed review guidance to keep later execution from guessing boundaries.
Yes, the planning approach supports scenario-first boundary I/O contracts for controller-facing plan artifacts. It creates decision-complete implementation plans as sequential executable plans with explicit execution phases and defined public contracts.
The best way to structure sequential executable plans is by generating decision-complete plans with explicit execution phases. This approach exposes concrete work bundles and public contracts before execution order, preventing later execution stages from guessing requirements.
burgebjRestrict Bash and text editing tools to a specified directory for the session.
ddaanetConvert design documents into structured runbooks with phase-aware typing.
SeoJaeWanIngest review inbox markdown files into raw evidence records and registry-backed pattern rules.
Eunho-JAutomate code changes by executing plans without debate or review phases.
