481건 · 관련도순
Audit a roadmap or backlog to distinguish outcomes from outputs. Use when the user says "outcome vs output", "escaping the build trap", "are we building the right things", "roadmap review", "feature factory", "output-driven team", "we keep shipping but nothing changes", or wants to shift focus from shipping features to delivering value - even if they don't explicitly say "outcome vs output".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read-only view of the execution roadmap. Lists every epic with its per-status tallies, nests the still-open rows beneath their epic, collapses wholly-finished epics into one rollup line, and closes by naming the next planned task in file order. Four verbs — `list` (the reader's view), `tasks` and `epics` (filterable row and epic queries), `next` (the first planned task). Invoke any time to see what is left to build. Not a workflow phase; never writes; never starts or commits work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or parallelizable task breakdown.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a risk register has treatment decisions but no plan anyone can execute, or when someone asks "write the risk treatment plan", "turn the risk register into actions", "what do we do about our high risks", "treatment plan for the auditor", "budget the security roadmap from the risks" or "our treatment plan is just a list of controls". Turns each reduce, avoid or transfer decision into dated actions with an owner, budget, dependency and the record that will prove it was done, states the expected residual score and why, and adds interim measures for risks that stay high while the work runs. Writes a CSV plan and a short notes file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user just says "plan", "planen" or "roadmap": offer a template via aos-plan-canvas templates. Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use for planning, whenever a user says "plan", "roadmap", "visualize the plan", "review the plan" or /plan-canvas, right after a brainstorm or grill interview has produced a plan, and whenever any skill's artifact (plan, design, comparison, report, diagram) can be reviewed visually instead of with typed feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Personal App-in-Skill voice-of-customer desk (Busabase App-in-Skill) aggregating user feedback from support email, Discord/Slack communities, X replies, app-store reviews, surveys, and interviews into clustered feature requests and a roadmap decision queue. Use when the user invokes $kelly-feedback or /kelly-feedback, or mentions user feedback, voice of customer, feature requests, roadmap decisions, feedback clustering, feedback triage, request dedupe, changelog replies, decline replies, or reviewing what users are asking for.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the status, progress, completeness, traceability, or next valid action of a PWDEV Power product roadmap is requested
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use quando o usuário quiser criar um GitHub Project — 'criar um project no github', 'novo board', 'project a partir de template', 'copiar project modelo' — a partir de um preset (roadmap-produto, kanban, scrum) apresentado e personalizável antes de criar, ou copiando um Project-modelo. Não use para publicar um roadmap (github-publish) nem para mexer em issues (github-issues).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create an approval-gated product requirements document or decompose an approved PRD into a traceable roadmap. Use for product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, or roadmap planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author a pull request an AI coding agent can actually get merged: a scoped, coherent diff; a Summary and Test Plan backed by real evidence; correct triage of required-and-blocking CI gates versus external/advisory checks (e.g. a Cloudflare Pages preview build); draft-while-WIP discipline; named fixup commits for real review findings; and a clean landing through a merge queue without force-pushing or bypassing branch protection. Use when opening, updating, triaging red CI on, or landing an agent-authored GitHub PR. NOT for this repo's internal release ceremony, actor embodiments, or contributor mirror-sync mechanics (use port-daddy-internal-dev), tracking backlog/issue lifecycle across a board (use agent-issue-tracker-workflow), or deciding what to build next / sequencing a roadmap (use legible-roadmap-with-sidequests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
개발 전에 제품의 목적을 검토하고 추진 여부, 첫 사용의 장애물, 기능 우선순위를 정리합니다. 근거와 다음 행동을 담은 기획서나 로드맵을 작성합니다.
제품 요청과 기획서를 개발에 필요한 구체적인 요구 사항으로 정리합니다. 업무 규칙, 데이터 소유권, 서비스 간 접점과 미결 사항을 문서로 남겨 다음 담당자에게 전달합니다.
대규모 기능 개발이나 마이그레이션 목표를 여러 차례 수행할 실행 계획으로 나눕니다. 단계별 배경, 의존 관계, 검증 방법을 정리해 다른 에이전트에게 작업을 인계할 수 있게 합니다.
최근 git 기록을 README·사양·제품 문서와 대조해 구현과 설명의 차이를 찾고, 기존 문체를 유지하며 최소한의 사실 수정 사항을 검토용 PR로 정리합니다.
메모와 분석 자료를 고객 제안, 기술 발표, 제품 발표용 HTML 슬라이드로 정리합니다. 테마 선택부터 발표 대본, 발표자 화면, PNG 출력까지 지원합니다.
새 기능 도입에 필요한 사용자 문제, 대안, 절충 사항과 성공 지표를 정리합니다. 어두운 배경의 HTML 슬라이드로 만들어 부서 간 검토를 돕습니다.
시스템 장애의 원인, 수정 내용, 재발 방지책을 HTML 슬라이드로 정리합니다. 전용 템플릿으로 발표 구성을 다듬어 기술 담당자와 경영진의 후속 대응 논의를 돕습니다.
제품 정보와 분석 결과를 16열 그리드와 하나의 강조색을 쓰는 HTML 슬라이드로 정리합니다. 22가지 고정 배치로 실제 데이터와 비교 내용을 전달합니다.