5.4천건 · 관련도순
Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Work through design or implementation choices one at a time, with concise context and clear alternatives. You can also review completed code change by change, recording decisions, approvals, and requested revisions in a final table.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn meeting notes, research, and business feedback into a one-page decision memo. Present a clear recommendation with confidence, supporting facts, option comparisons, risks, and next steps so decision-makers can assess the choice quickly.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Classify agent work as ready to continue, needing human judgment, or intentionally paused. Structure decision requests with evidence, a recommended choice, and clear outcomes, then connect the recorded decision to the next responsible agent.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize software project documents from proposals through decisions, implementation specs, and incident reviews. Defines document status changes, links between records, and checks that help teams maintain related guides and preserve decision history.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。 English: Criticism and self-criticism. After delivery, at a review checkpoint, on receiving criticism, or when the same mistake recurs, examine the result and the process honestly and concretely, produce actionable fixes, and accept valid criticism without defensiveness. Triggers include review, retrospective, audit, "check this for problems", "are you sure"; skip at the start of a task or for one-step lookups.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection, secure configuration, account management, access control, continuous vulnerability management, audit log management, email and web browser protections, malware defenses, network infrastructure management, network monitoring and defense, application software security, incident response, penetration testing, and CIS Controls mapping to NIST CSF, ISO 27001, SOC 2, and CMMC. Use for any question about CIS Controls, CIS Benchmarks, Implementation Groups, or prioritized cyber hygiene for any organization size.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection, secure configuration, account management, access control, continuous vulnerability management, audit log management, email and web browser protections, malware defenses, network infrastructure management, network monitoring and defense, application software security, incident response, penetration testing, and CIS Controls mapping to NIST CSF, ISO 27001, SOC 2, and CMMC. Use for any question about CIS Controls, CIS Benchmarks, Implementation Groups, or prioritized cyber hygiene for any organization size.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured approaches to decisions under uncertainty and complexity. Covers expected value, decision trees, multi-criteria decision analysis, System 1 vs System 2 allocation, pre-mortems, reversible vs irreversible decisions, and the distinction between good decisions and good outcomes. Use when choosing among alternatives with uncertain or multi-dimensional consequences, especially when the stakes justify a deliberate rather than intuitive process.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company must test its incident response or continuity plan without breaking anything, because an audit, a customer, a regulator or the plan itself calls for an exercise, and someone asks "design a tabletop", "run a ransomware tabletop", "BCP exercise", "crisis simulation", "test our incident response plan", "write the injects" or "we need exercise evidence". Picks two or three objectives, builds a realistic company-specific scenario with timed injects that force decisions, briefs the facilitator and observers, and writes the exercise plan, the injects, the observer sheet and a findings record that ends in owned actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architecture Decision Records (ADR) — a lightweight method for capturing important architectural decisions with context, trade-offs, and rationale. Based on Michael Nygard's ADR pattern and Google/Meta/ByteDance's design documentation culture. USE WHEN: deciding between technology choices, designing new architecture, changing existing architecture, documenting why a decision was made, onboarding new team members, or preserving design context for future maintainers. Triggered by terms like "tech choice", "architecture decision", "why did we choose", "design rationale", "ADR", or "architectural decision record".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
여러 관점으로 정리한 중요한 의사결정 초안에 Codex의 외부 비평을 한 차례 추가합니다. 결론의 약점, 누락된 실패 가능성, 반대 의견의 반영 여부를 확인합니다.
혼자 결정하기 어려운 문제를 전문가나 관계자에게 전달할 질문지로 정리합니다. 상대의 지식과 필요한 답변을 확인해 회의나 개별 응답에 쓸 Markdown 문서를 만듭니다.
판단할 문제를 한 문장으로 정리하고 세 가지 선택지의 장단점과 권고안을 제시합니다. 완료 기준과 실행 절차도 함께 정리해 팀에 공유할 제안서 작성을 돕습니다.
설계 결정의 이유와 비교한 대안을 기록하고 README, API 문서, 변경 이력을 정리합니다. 새 담당자와 AI 에이전트가 구현 배경을 이해하도록 돕습니다.
도시 녹지와 나무의 수관 면적 확대 정책을 시의회와 행정 심사용 HTML 슬라이드로 만듭니다. 공공의 필요성, 근거, 정책 선택지, 자금 결정을 정리합니다.
OpenDesign에서 자신의 API 키로 모델을 선택하는 방법을 설명하는 HTML 슬라이드를 만듭니다. 터미널형 템플릿으로 비용, 품질, 모델별 용도 판단을 돕습니다.
인터뷰, 문의, 설문을 정리해 제품과 디자인 결정에 쓸 HTML 화면을 만듭니다. 근거, 주제, 확신 수준, 개선안 비교와 다음 실험을 함께 제시합니다.
Create AgentDB learning plugins that use recorded experience to improve agent decisions. Choose a learning method, store states, actions, and rewards, train models, and evaluate suggested actions through CLI and API workflows.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.