Product & Planning

modu-ai Skill

새 페이지·콘텐츠·캠페인을 위해 네이버·구글·AI 검색(GEO)에서 노릴 키워드를 발굴하고, 검색 의도·경쟁도·롱테일로 분류해 토픽 클러스터로 묶어 드립니다. 다음과 같은 요청 시 사용하세요: - "이 주제로 뭐 쓸지 키워드 뽑아줘" - "검색 의도별로 키워드 분류해줘" - "롱테일 키워드 발굴해줘" - "토픽 클러스터 설계해줘 (필러+클러스터 구조)" - "네이버·구글·ChatGPT에서 노릴 키워드 리서치해줘" - "경쟁 낮고 검색량 있는 키워드 찾아줘" - "AI 검색이 인용할 만한 질의(query) 후보 뽑아줘" 검색 의도 4분류·롱테일·키워드 난이도·쿼리 팬아웃(query fan-out)·토픽 클러스터 프레임으로 키워드 목록과 클러스터 맵을 만들고, 서술형 권고는 moai-coworker:ai-slop-reviewer → moai-writer:korean-humanize으로 다듬습니다. [책임 경계] vs moai-marketer:marketing-seo-audit: 이 스킬=쓸 키워드·클러스터를 새로 발굴(discovery), 저 스킬=이미 있는 페이지·사이트의 SEO 건강도를 진단(audit). 키워드를 정한 뒤 페이지를 점검하려면 marketing-seo-audit로 넘어갑니다.

wenjunduan Skill

PACE 可选 stage. 大需求 (跨 ≥3 模块) 拆成子 feature 序列. 产出 .ai_state/roadmap/{slug}/items.yaml + roadmap.md. 每个子 item 完成后回写 status, 主 agent 自动进入下一个 item 的 plan stage.

wenjunduan Skill

PACE 可选 stage. 大需求 (跨 ≥3 模块) 拆成子 feature 序列. 产出 .ai_state/roadmap/{slug}/items.yaml + roadmap.md. 每个子 item 完成后回写 status, 主 agent 自动进入下一个 item 的 plan stage.

wenjunduan Skill

PACE 可选 stage. 大需求 (跨 ≥3 模块) 拆成子 feature 序列. 产出 .ai_state/roadmap/{slug}/items.yaml + roadmap.md. 每个子 item 完成后回写 status, 主 agent 自动进入下一个 item 的 plan stage.

wenjunduan Skill

PACE 可选 stage. 大需求 (跨 ≥3 模块) 拆成子 feature 序列. 产出 .ai_state/roadmap/{slug}/items.yaml + roadmap.md. 每个子 item 完成后回写 status, 主 agent 自动进入下一个 item 的 plan stage.

wenjunduan Bundle

PACE 可选 stage。需求跨 3 个以上模块、需要拆成子 feature 序列时触发。

wenjunduan Bundle

PACE 可选 stage。至少两个可独立验收交付切片或用户明确要求拆分时触发。

wenjunduan Skill

PACE 可选最早 stage. 用户想法模糊时通过对话理清楚. AI 角色: 思考伙伴, 挖用户真正想解决的问题, 必要时提出更好的替代方案. 完成后产出 sprints/{date}-{slug}/brainstorm.md 并路由到 plan / roadmap / direct design.

wenjunduan Skill

PACE 可选最早 stage. 用户想法模糊时通过对话理清楚. AI 角色: 思考伙伴, 挖用户真正想解决的问题, 必要时提出更好的替代方案. 完成后产出 sprints/{date}-{slug}/brainstorm.md 并路由到 plan / roadmap / direct design.

wenjunduan Skill

PACE 可选最早 stage. 用户想法模糊时通过对话理清楚. AI 角色: 思考伙伴, 挖用户真正想解决的问题, 必要时提出更好的替代方案. 完成后产出 sprints/{date}-{slug}/brainstorm.md 并路由到 plan / roadmap / direct design.

wenjunduan Bundle

Use when a business requirement must be delivered through the full-stack PACE loop: requirements, roadmap, design checkpoints, frontend demo, database schema, backend module, tests, integration, review, E2E, security, delivery report, and human confirmation. It orchestrates existing skills and evidence; it does not implement code or create a second state machine.

wenjunduan Bundle

Use when a business requirement must be delivered through the full-stack PACE loop: requirements, roadmap, design checkpoints, frontend demo, database schema, backend module, tests, integration, review, E2E, security, delivery report, and human confirmation. It orchestrates existing skills and evidence; it does not implement code or create a second state machine.

apideck-libraries Skill

Front-door skill for the Apideck MCP server — 330 unified-API tools across 10 domains plus 4 intent-grouped workflow tools, exposed via dynamic discovery. Use when the user is building an MCP-based agent (Claude Code, OpenAI Agents SDK, Pydantic AI, LangChain) and wants to integrate with any of the 200+ SaaS connectors Apideck covers. Hosted at mcp.apideck.dev/mcp; stdio transport via `npx -y @apideck/mcp` for local development.

modu-ai Bundle

제품 기획 문서(PRD·기능 명세서)와 AI 도입 전략 보고서를 만들어 드립니다. 다음과 같은 요청 시 사용하세요: - "PRD 작성해줘" - "기능 명세서 만들어줘" - "AI 도입 전략 보고서 써줘" - "제품 기능 우선순위 정리해줘" - "디지털 전환 로드맵 수립해줘" 기획 의도와 요구사항을 검토 가능한 문서로 정리하고, ai-slop-reviewer·korean-humanize으로 마무리할 수 있습니다. [책임 경계] 정부·지원사업 신청서는 moai-consultant:consult-gov-grant, R&D·연구비 과제는 moai-tutor:education-grant-writer로 라우팅

modu-ai Bundle

프로젝트 로드맵·마일스톤 계획과 전략적 제휴(MOU) 초안, ESG 지속가능성 감사·DEI 전략 문서를 만들어 드립니다. 다음과 같은 요청 시 사용하세요: - "로드맵 정리해줘" - "마일스톤 계획 세워줘" - "MOU 초안 작성해줘" - "ESG 지속가능성 감사 해줘" - "DEI 정책 도입 로드맵 설계해줘" - "분기별 마일스톤과 담당자 정리해줘" 일정·리소스·파트너십·지속가능성 계획을 실행 가능한 문서로 정리하고, ai-slop-reviewer·korean-humanize으로 마무리할 수 있습니다. [책임 경계] 운영 케이던스(주간보고·스탠드업·회고·OKR 추적)는 moai-pm, 본 스킬은 제품 발견·로드맵/마일스톤 기획

modu-ai Bundle

한국 팀의 주간 비즈니스 리뷰(WBR) 보고서 자동 생성 스킬입니다. 일일 노트·완료 태스크·KPI 데이터를 입력받아 임원/팀 두 버전(격식체/구어체)으로 작성합니다. Notion·Linear·Asana·Slack MCP가 가용하면 자동 데이터 fetch, 없어도 자유 텍스트 입력 fallback. 다음과 같은 요청 시 반드시 이 스킬을 사용하세요: - "주간보고 작성", "WBR 준비", "이번 주 한 일 정리" - "주간 회의 자료", "위클리 리포트", "주간 업무 보고" - "임원 주간보고", "팀 주간보고" [책임 경계] 제품 발견·로드맵/마일스톤 기획은 moai-coworker:collab-roadmap, 본 스킬은 운영 케이던스(주간보고)

crestapps Bundle

Skill for configuring localization and multi-language support in Orchard Core. Covers culture settings, content localization, PO file contexts and discovery locations, IStringLocalizer, the Liquid t filter, and the admin culture picker. Use this skill when requests mention Orchard Core Localization, Configure Localization and Multi-Language Support, Enabling Localization Features, Localization Settings via Recipe, PO File Format, PO File Location Convention, or closely related Orchard Core implementation, setup, extension, or troubleshooting work.

crestapps Bundle

Skill for discovering rendered Orchard Core shapes and selecting safe frontend or admin theme overrides. Covers shape debug comments, bindings, alternates, differentiators, display types, field display modes, OrchardCore.Placements, OrchardCore.Templates, OrchardCore.AdminTemplates, OrchardCore.Liquid, and runtime visual theming workflows. Use when an AI must identify the exact shape behind existing HTML, create a targeted template or placement override, or redesign a running Orchard Core tenant without guessing shape names.

crestapps Skill

Skill for Liquid-based prompt templates, template discovery, and prompt composition in CrestApps.Core.

modu-ai Skill

목표를 막연한 다짐이 아니라 실천 가능한 계획으로 바꿔주는 스킬입니다. '신년 목표 세워줘', '12주 계획법으로 쪼개줘', '만다라트 만들어줘', '개인 OKR', '목표를 실천으로'처럼 말하면 됩니다. 12주 계획·만다라트·개인 OKR 등으로 목표를 잘게 나누고 주간 루틴까지 연결해, "세웠는데 안 하는" 목표를 줄여줍니다.

modu-ai Bundle

사업계획서·비즈니스 모델·신시장 진출 같은 전략 문서를 검증된 프레임워크(SWOT·린 캔버스·블루오션·OKR 등)로 정리해 만들어 드립니다. 다음과 같은 요청 시 사용하세요: - "사업계획서 써줘" - "비즈니스 모델 만들어줘" - "SWOT 분석해줘" - "린 캔버스 작성해줘" - "블루오션 전략 세워줘" - "OKR 설정해줘" - "해외 진출 전략 짜줘" 현황 분석·전략 프레임워크·전략 방향·실행 로드맵 구조로 작성하며, PPT 변환이나 AI 표현 다듬기로 이어집니다.

modu-ai Bundle

KPI 대시보드와 운영 현황 보고서를 자동으로 생성합니다. "주간 보고서 작성해줘", "KPI 현황 정리해줘", "월간 성과 보고서 만들어줘"라고 요청할 때 사용하세요. 주간·월간·분기 보고서, OKR 현황, 마일스톤 진행률, 이슈 및 리스크 매트릭스를 지원합니다.

modu-ai Bundle

성과평가 체계를 설계하고 실행을 도와주는 스킬입니다. "OKR 설정해줘", "성과 리뷰 템플릿 만들어줘", "피드백 면담 스크립트 써줘"처럼 말하면 됩니다. MBO·OKR·KPI 체계 구축, 360도 평가 설계, 인사 고과 가이드, 피드백 면담 스크립트 작성을 지원합니다.

codyswanngt Bundle

Decompose a single PRD or specification into ordered work items in the configured tracker. Vendor-agnostic — the source can be a Notion PRD URL, a Confluence PRD URL, a Linear project URL, a GitHub Issue URL, an existing JIRA epic key, a markdown file, or a free-form description; the destination tracker is whatever the project is configured to use via `.lisa.config.json` `tracker` (JIRA, GitHub Issues, or Linear). Single-PRD mode only — for batch scanning of all Ready PRDs in a queue, use the lisa-intake skill.

codyswanngt Bundle

Vendor-agnostic scanner for Ready queues. Notion PRD database URL → first Ready PRD → lisa-plan. Confluence space or parent page URL → first prd-ready PRD → lisa-plan. Linear workspace URL or team key → first prd-ready project → lisa-plan. GitHub repo URL or `org/repo` token → first prd-ready issue → lisa-plan, or first `status:ready` issue → lisa-implement when `tracker = github`. JIRA project key or JQL filter → first Ready ticket → lisa-implement. On the PRD side it also closes the loop: each cycle rolls a ticketed PRD up to shipped and dispatches lisa-verify-prd for one shipped PRD (shipped → verified on pass; on fail, re-opened shipped → ticketed with build-ready fix tickets that auto-build and re-verify — never blocked). Designed as the cron target for /schedule — one eligible item per invocation, exits cleanly on empty. Symmetric counterpart to the single-item lisa-plan and lisa-implement skills.

codyswanngt Bundle

Run the Debrief flow over a shipped initiative. Input: a PRD URL (Notion / Confluence / Linear / GitHub Issue / file), a JIRA epic key, or a GitHub epic issue URL. Output: a triage-ready learnings document covering every work item in the initiative — edge cases, gotchas, process friction, tooling gaps, convention drift — each with structured evidence and a human-disposition field. Persistence is deferred to lisa-debrief-apply.

codyswanngt Bundle

Research a problem space and create a PRD in the configured PRD source. Investigates the codebase, defines user flows, assesses technical feasibility, synthesizes the spec, then creates it in the source (Notion / Confluence / GitHub / Linear per .lisa.config.json `source`) via lisa-prd-source-write — there is no loose document artifact. Vendor-agnostic. Accepts an optional `prd_ready` flag (default false → the PRD is created in the `draft` role; true → created `ready` so lisa-intake auto-claims it) and an optional dedupe `marker`/`dedupe_key` (used when invoked by lisa-project-ideation) so re-runs reference the existing PRD instead of duplicating it.

codyswanngt Bundle

Initiative-level PRD acceptance gate. Given a PRD ref/URL (GitHub, Linear, Notion, Confluence, or JIRA), resolves the source vendor, reads the PRD and its generated top-level child work via the prd-lifecycle-rollup contract, and confirms every required child is terminal before any verification runs — if any is non-terminal it reports the incomplete set and STOPS. When the guard passes it runs spec-conformance against the original PRD requirements plus empirical verification via verification-lifecycle. On CONFORMS with all checks passing: transitions the PRD shipped → verified and posts evidence. On PARTIAL/DIVERGES or any failing check: re-opens the PRD shipped → ticketed (NEVER blocked), creates build-ready fix tickets for each divergence, and posts a product-readable failure report — the fix tickets auto-build, rollup re-ships the PRD, and a later intake cycle re-verifies, so the loop closes itself. Idempotent re-runs: comments regenerate in place via sentinel markers; fix tickets dedupe by stable ref.

codyswanngt Bundle

Update a source PRD with an always-written, machine-readable `## Tickets` (alias `## Generated Work`) section linking back to every work item created from it. Each entry carries a parseable ref + URL + type + parent token so the generated child set is readable without scraping prose. Vendor-aware on the source side (Notion / Confluence / Linear / GitHub Issue / file) and tracker-agnostic on the ticket side; the documented section is written for every vendor, additive to native hierarchy linking. Idempotent — regenerates the section on each run rather than appending, so re-planning never accumulates stale links. Invoked by the *-to-tracker skills at the end of their pipeline and standalone if a PRD's Tickets section needs to be refreshed.

codyswanngt Bundle

Read-only operator surface for the current project's PRD and build backlog health. Resolves the configured PRD source and build tracker from the same Lisa contract used by intake and repair, summarizes lifecycle-role counts, distinguishes idle queues from setup problems, and highlights actionable blocked, in-review, claimed, or shipped work.

codyswanngt Bundle

Configure GitHub Issues as the destination tracker and/or the PRD source for this project. Verifies the gh CLI is installed and authenticated, resolves `org/repo`, scaffolds the build-queue label namespace (`status:*`) when GitHub is the tracker and/or the PRD-lifecycle label namespace (`prd-*` + sentinel) when GitHub is the PRD source, writes the `github` section into `.lisa.config.json`, and offers to set top-level `tracker: "github"` and/or `source: "github"`. Idempotent — re-running updates the existing section and reuses existing labels rather than duplicating. No /lisa:setup:atlassian prerequisite (GitHub auth is standalone).

codyswanngt Bundle

Configure Linear as the destination tracker and/or the PRD source for this project. Verifies Linear access (MCP OAuth or a personal API key in OS keychain), resolves the workspace slug and team key, scaffolds the build-queue issue-label namespace (`status:*`) when Linear is the tracker and/or the PRD-lifecycle project-label namespace (`prd-*` + issue-level sentinel) when Linear is the PRD source, writes the `linear` section into `.lisa.config.json`, and offers to set top-level `tracker: "linear"` and/or `source: "linear"`. Idempotent — re-running updates the existing section and reuses existing labels. No /lisa:setup:atlassian prerequisite.

codyswanngt Bundle

Configure Notion as the PRD source for this project. Walks the user through creating an internal integration in the target workspace, sharing the PRD database with it, stores the resulting `ntn_*` token in OS keychain (multi-workspace-safe — keyed by workspaceId), validates against the Notion API, and writes `notion.workspaceId`, `notion.prdDatabaseId`, and `notion.values` into `.lisa.config.json`. Idempotent — re-runs update the existing section rather than duplicating it. Offers to set top-level `source: "notion"`.

codyswanngt Bundle

Vendor-agnostic repair scanner — the recovery counterpart to lisa-intake. Finds work that got stuck or was left half-closed across the same queues lisa-intake serves (Notion / Confluence / Linear / GitHub PRDs; JIRA / GitHub / Linear build queues): items left in `blocked`, work stalled in an in-progress role (build `claimed`, PRD `in_review`), terminal-labeled items still natively open, and rollups whose children are all terminal. Repairs every actionable candidate up to `max_candidates`: resumes stalled work in place (diagnosing a stalled build's PR/deploy state first — merged PRs get the missed env transition, behind-base PRs are re-synced, unmergeable PRs or failed deploys get a build-ready fix ticket + `blocked`), re-validates blocked PRDs and build items whose blockers cleared, performs terminal native closure, and reconciles parent rollups to their derived state. Idempotent and loop-protected; never mutates `draft`/`verified` or `ready` leaves. A /schedule cron target alongside lisa-intake.

jmagly Skill

AUTO-INVOKE when user mentions SDLC, requirements, architecture, ADR, use case, user story, test plan, phase gate, inception, elaboration, construction, transition, intake, deploy. SDLC framework quick reference — phase model, capability domains, and curated discovery phrases for aiwg discover.

jmagly Skill

Orchestrate Discovery Track flow to prepare validated requirements and designs one iteration ahead of delivery