'standup' 검색 결과

Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record written since its own cursors, turns the member's ticks into sent rows and closed cards, folds the card inbox, re-renders the pipeline board, and writes the short morning brief the member opens first. It names the veto window every day. It holds every outbound action unless you released the channel, and it never touches a credential.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record, turns yesterday's ticks into sent dates and closed cards, folds the card inbox, rewrites the launch board, and writes the short morning brief the member opens first. It holds every outbound action unless you released the channel, and it never touches a credential.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and execute effective sprints using Agile methodologies. Define sprint goals, estimate user stories, manage sprint backlog, and facilitate daily standups to maximize team productivity and deliver value incrementally.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user needs a standup-ready summary of recent project activity from local evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when Compass state, standup briefs, or executive summaries need interpretation for the active Odylith slice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interpret Compass state, standup briefs, and executive summaries for the active Odylith slice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build multi-project RAID and RAG views for portfolios, programs, or cross-functional workstreams. Use when PMOs, program managers, or leaders need a real status picture across milestones, dependencies, owners, and escalations. Do not use for a single standup note, one issue ticket, or generic meeting minutes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Phase 10.6 — sync the project's execution roadmap (project.json → roadmap.path, default docs/roadmap-execution-plan.md) to the just-landed work. Flips the tasks named in workflow.json → roadmap_tasks[] from ⬜ to ✅ and promotes their epic headings ⬜→🟡→✅, preserving the standup parser format contract. On the epic track it appends instead — the epic's heading plus one row per slice — and stamps roadmap_epic back into the epic state. Also hosts the ad-hoc backfill that puts every epic already on disk onto the roadmap. Fail-open: never throws, no-ops when roadmap.path is unset/absent or no task matches, and never blocks a commit. Runs after /archive and before /memory-sync on every committing track.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Synthesise a status, standup, or situation-report from current work state. Trigger when a team member needs a concise summary of where things stand, what is blocked, and what is next.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Brief on concurrent sessions — who else is working, in which repos, on which files, and what landed underneath you. Use when a commit appears that you did not make, before touching a shared file, or when orienting mid-task in a busy workspace.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stand up or rebuild an AWS Shifter tenant end to end (teardown, bootstrap, secrets, image bakes, deploy via the real deploy.yml dispatch, health check, base-range smoke, and a POLARIS range walkthrough). AWS only. Use when asked to rebuild, redeploy, or stand up an AWS tenant such as proof or aws-dev from a clean state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

デイリースタンドアップレポートを生成してSlackに投稿する。GitHub Issues から進捗を取得する

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: Good morning Team, start-of-day briefing, or morning status request. Architect orchestrates; Builder, Tester, and Router return their sections as subagents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Founder and CEO automation — morning standup, overnight cycle, burn rate, runway, pipeline review, investor and fundraising prep, executive summary, daily digest. Operates on the .mxm-executive-summary context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.