菜单
Write technical specifications (tech specs): goals, scope, architecture, components, APIs, data models, database migrations, feature flags, risks, and rollout. Use when the user asks for a tech spec, technical design, architecture doc, design document, or when planning database changes or rollout strategies.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/micaelmalta/agentic --skill architect命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | architect |
| description | Write technical specifications (tech specs): goals, scope, architecture, components, APIs, data models, database migrations, feature flags, risks, and rollout. Use when the user asks for a tech spec, technical design, architecture doc, design document, or when planning database changes or rollout strategies. |
| triggers | ["/architect","tech spec","technical spec","technical design","architecture doc","design document","write a tech spec","system design","design the solution","database migration","schema change","feature flag","rollout strategy"] |
"Spec before build: align stakeholders and unblock implementation."
A tech spec captures what will be built, how it fits together, and what the team will deliver. It is written before or alongside implementation and is the single reference for scope and design.
Always use the template when writing a tech spec. Read it first, then fill it in:
skills/architect/tech_proposal_template.mdThe template covers: metadata (PRD link, priority, timing, owner, status), architecture considerations and expected flow, API changes (new/edit endpoints, OpenAPI, Spectral), data models, domain architecture, additional considerations (actors, permissions, unknowns, risks), and estimation & implementation plan (effort, teams, rollout, metrics, impact). Align your tech spec with these sections; add or rename subsections only to match project conventions.
When the feature involves schema changes, include a Database Migration Plan:
| Aspect | Document |
|---|---|
| Schema changes | New tables, columns, indexes, constraints; use migration tool syntax (e.g., Prisma, Alembic, Flyway, goose) |
| Data migrations | Backfills, transformations, default values for existing rows |
| Rollback strategy | How to reverse the migration if deployment fails; what data loss is acceptable |
| Deployment order | Whether migration runs before, during, or after code deploy; zero-downtime considerations |
| Testing | How to test migration locally and in staging; seed data requirements |
Zero-downtime migrations: For high-availability systems, plan migrations in phases:
When gradual rollout is needed, include a Feature Flag Plan:
| Aspect | Document |
|---|---|
| Flag name | Descriptive, consistent with project naming (e.g., enable_new_checkout_flow) |
| Flag type | Boolean, percentage, user segment, or variant (A/B) |
| Default state | Off in production initially; on in dev/staging |
| Rollout stages | Internal → beta users → percentage ramp → 100% |
| Kill switch | How to disable quickly if issues arise |
| Cleanup | When and how to remove the flag after full rollout |
Flag placement: Identify where in code the flag check goes (API layer, service layer, UI) and what behavior changes per state.
docs/tech-specs/YYYY-MM-DD-<feature-or-epic>.md or context/tech-specs/.skills/architect/tech_proposal_template.md in the output document.No mandatory commands. Use RLM or codebase search when you need to describe current architecture or affected components. Use para /plan for the implementation plan; the tech spec is the design document the plan implements.
/plan): Ordered steps and tasks to build it; audience is eng.| Situation | Skill to invoke | How |
|---|---|---|
| Tech spec needs implementation plan | para skill | Read skills/para/SKILL.md, use /plan |
| Design has security implications | security-reviewer skill | Read skills/security-reviewer/SKILL.md |
| Architecture needs documentation (ADR) | documentation skill | Read skills/documentation/SKILL.md |
| Design includes CI/CD pipeline | ci-cd skill | Read skills/ci-cd/SKILL.md |
| Performance requirements in design | performance skill | Read skills/performance/SKILL.md |
| Large codebase requires exploration | rlm skill | Read skills/rlm/SKILL.md |
Complete development workflow from planning to GitHub PR using PARA methodology and RLM for large codebases. Use when implementing a feature, fixing a bug, refactoring, or taking work from plan to GitHub PR.
Analyze and improve performance: profile, find bottlenecks, optimize, and instrument code with observability for diagnosing performance issues (profiling, bottleneck tracing). Use when the user asks about performance, slow code, bottlenecks, profiling, optimization, or adding performance-specific observability.
Design and implement tests (unit, integration, e2e, accessibility, i18n), improve coverage, and run test suites. Use when the user asks to add tests, write tests, improve coverage, run tests, test accessibility, test translations, or implement test strategy.