project-architect

스타9

포크1

업데이트2026년 2월 2일 02:32

Create comprehensive architectural documentation for complex features or projects requiring multiple components, clear API design, and phase-based implementation. Use when starting complex features (3+ days work) that need system design, component specifications, or multi-phase planning. Creates architecture docs in ai-docs/architect/ defining system components, data flow, API contracts, and implementation phases. Triggers on "design the architecture for...", "create system design for...", or complex feature requests after PRD exists.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

jackzhaojin

jackzhaojin/continuous-agent

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Project Architect

Create architectural documentation that defines HOW a system will be built at a high level.

When to Use

Use this skill when:

PRD exists and is approved
Feature requires multiple components or systems
Clear API design is needed
Phase-based implementation is required
Architectural decisions need documentation

Do NOT use for:

Simple bug fixes or small features (< 1 day)
When no PRD exists (use prd-writer first)
Detailed task-level instructions (use task-breakdown)

Workflow

1. Read the PRD

Start by reading the PRD to understand requirements, constraints, and success criteria.

2. Gather Technical Context

Ask clarifying questions:

Existing Patterns: What similar features exist in the codebase?
Technology Choices: Any required tech stack or frameworks?
Performance Needs: Response time, scalability targets?
Integration Points: What external systems are involved?

3. Design the Architecture

Create ai-docs/architect/{feature-name}-architecture.md using template from references/architecture-template.md.

Key sections:

Overview: Purpose, goals, scope
System Architecture: Components, data flow, integration points
Technical Design: Tech stack, API design, component specs
Security & Performance: Key considerations
Implementation Phases: Logical order for building

4. Validate

Review with user before proceeding to task breakdown.

Best Practices

Start with WHY: Reference the PRD's business value
Be Specific: File paths, function names, data structures
Show Trade-offs: Document alternatives and why they were rejected
Think in Phases: Break complex features into stages
Reference Examples: Point to similar existing patterns
Component-First: Define clear boundaries and interfaces

Example

User: "Design the architecture for a real-time collaboration feature"

You: [Asks about existing patterns, tech preferences, performance needs]

Then creates: ai-docs/architect/realtime-collaboration-architecture.md with WebSocket design, state management, conflict resolution, and 3-phase implementation plan.

Resources

references/architecture-template.md - Full template with all sections

이 저장소의 다른 Skills

같은 저장소

memory-harvester

jackzhaojin/continuous-agent

The SOLE WRITER to the V3.0 mem0 second brain. Invoked agentically by the executive at write moments — post-run, post-retro, post-spec-merge, manual /harvest. Decides which facts to classify into which memory type (principle/semantic/procedural/episodic/reflective), validates against the schema, and calls the deterministic plumbing in references/ via Bash. Blocks until writes are durable (poll event endpoint for SUCCEEDED). Never invoked from worker code.

2026-05-319

memory-reader

jackzhaojin/continuous-agent

Consult the V3.0 mem0 second brain agentically during executive planning, work selection, pre-spawn memory pack building, and failure diagnosis. Use this skill whenever the executive needs to remember prior runs, retros, or learned principles. Read-only — never writes. Drives the unified `mem0` CLI via Bash, orchestrating multiple iterative search queries (mem0 does not do multi-hop graph traversal natively, so iterative search IS the multi-hop).

2026-05-319

memory-hook-failure-diagnosis

jackzhaojin/continuous-agent

Hook D — Failure-Diagnosis memory consultation. Runs at executive Phase 7 (after 3+ consecutive failures on a work item) BEFORE the failure-diagnosis skill itself runs. Consults the second brain for similar prior failures and successful retry strategies, then hands enriched context to the failure-diagnosis skill. Read-only. Invokes the memory-reader skill.

2026-05-169

memory-hook-post-retro-harvest

jackzhaojin/continuous-agent

Hook E — Post-Retrospective Harvest. Runs after a retrospective markdown doc completes (per-run or weekly). Reads the retro fully and decides which durable lessons (reflective, semantic, procedural memories) to write to the second brain. Typically 3–8 writes per weekly retro, 0–3 per per-run retro. Invokes the memory-harvester skill for the actual writes.

2026-05-169

memory-hook-post-run-harvest

jackzhaojin/continuous-agent

Hook C — Post-Run Harvest. Runs after a worker completes (executive Phase 6 success path). Decides agentically which facts from the run to write to the second brain — typically 0–3 memory writes per run (one episodic, optionally a semantic or procedural). Invokes the memory-harvester skill to do the actual writes (with event-polling for durability).

2026-05-169

memory-hook-pre-spawn-pack

jackzhaojin/continuous-agent

Hook B — Pre-Spawn Memory Pack build. Runs before each worker spawn (executive Phase 4 prep). Reads the second brain for project-specific memories and produces a Memory Pack markdown block that worker-spawner injects into the worker's generated CLAUDE.md. Workers consume this as static markdown — they never call mem0 themselves. Read-only. Invokes the memory-reader skill.

2026-05-169

name

project-architect

description

Project Architect

Create architectural documentation that defines HOW a system will be built at a high level.

When to Use

Use this skill when:

PRD exists and is approved
Feature requires multiple components or systems
Clear API design is needed
Phase-based implementation is required
Architectural decisions need documentation

Do NOT use for:

Simple bug fixes or small features (< 1 day)
When no PRD exists (use prd-writer first)
Detailed task-level instructions (use task-breakdown)

Workflow

1. Read the PRD

Start by reading the PRD to understand requirements, constraints, and success criteria.

2. Gather Technical Context

Ask clarifying questions:

Existing Patterns: What similar features exist in the codebase?
Technology Choices: Any required tech stack or frameworks?
Performance Needs: Response time, scalability targets?
Integration Points: What external systems are involved?

3. Design the Architecture

Create ai-docs/architect/{feature-name}-architecture.md using template from references/architecture-template.md.

Key sections:

Overview: Purpose, goals, scope
System Architecture: Components, data flow, integration points
Technical Design: Tech stack, API design, component specs
Security & Performance: Key considerations
Implementation Phases: Logical order for building

4. Validate

Review with user before proceeding to task breakdown.

Best Practices

Start with WHY: Reference the PRD's business value
Be Specific: File paths, function names, data structures
Show Trade-offs: Document alternatives and why they were rejected
Think in Phases: Break complex features into stages
Reference Examples: Point to similar existing patterns
Component-First: Define clear boundaries and interfaces

Example

User: "Design the architecture for a real-time collaboration feature"

You: [Asks about existing patterns, tech preferences, performance needs]

Then creates: ai-docs/architect/realtime-collaboration-architecture.md with WebSocket design, state management, conflict resolution, and 3-phase implementation plan.

Resources

references/architecture-template.md - Full template with all sections