'milestone' 검색 결과

Design, review, and implement Gantt charts for project schedules. Assess source data, task dependencies, and resource needs, then define suitable views, editing behavior, rendering tools, accessibility, exports, and tests—or recommend a clearer alternative.

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

• Choose between a Gantt chart, Kanban board, or timeline
• Map project-management exports into schedule data
• Review dependencies, critical path, and baseline variance

Compare a Linear issue and its acceptance criteria with implementation evidence. Identify gaps, retain links to tests and pull requests, and update progress only when the relevant implementation, review, or deployment milestone is supported.

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

• Comparing acceptance criteria with implementation evidence
• Checking gaps before updating a Linear issue
• Adding links to pull requests, tests, and releases

Add personality to interfaces through small interaction responses, completion animations, illustrations, and product-specific messages. Shape enjoyable moments around the brand and user context while preserving task flow, accessibility, and performance.

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

• Refining button and form feedback
• Adding personality to empty and loading states
• Celebrating completions and milestones

Develop a vague research interest into a specific question and plan. Use 5W1H prompts, literature reviews, and analysis of unanswered questions to define hypotheses, required evidence, suitable methods, and a concrete next step.

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

• Exploring research ideas with 5W1H prompts
• Reviewing literature to find unanswered questions
• Defining hypotheses and evidence requirements

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

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

• Proposing a major architecture change
• Replanning milestones after a foundation change
• Comparing technical options before seeking approval

Get reminders to compact conversation context, meaning summarize it for continued work, during long Claude Code sessions. A tool-call counter prompts consideration of manual compaction, with guidance on choosing useful breaks between task phases.

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

• Compact context between research and implementation
• Organize context after a milestone
• Clear debugging context before continuing

Turn a research interest into a defined question and practical plan. Use structured brainstorming, literature review, gap analysis, and method comparison to produce a research proposal, organized review, and references, with Zotero support for paper management.

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

• Develop a research topic using 5W1H
• Organize literature and identify unanswered questions
• Compare research methods and required resources

Keep research progress and project plans aligned in Obsidian. Record daily work and meeting outcomes, turn lasting commitments into checklists, and move durable findings into existing project notes while preserving the daily history.

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

• Recording daily research progress
• Turning lasting TODOs into plan checklists
• Organizing meeting outcomes by their lasting value

Keep research progress, decisions, and pending checkpoints across sessions. Store project context locally, recover essential details when returning, and track why decisions changed so research work can resume with a clear next step.

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

• Resuming research after a break
• Reviewing decisions and their rationale
• Checking pending research milestones

Coordinate 15 agents implementing claude-flow v3 across security, core systems, integration, testing, performance, and release work. Provides role assignments, task dependencies, GitHub tracking examples, and a four-phase schedule spanning 14 weeks.

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

• Assign claude-flow v3 work across 15 agents
• Run tasks in parallel while respecting dependencies
• Track milestones and progress through GitHub issues

Manage work records in BB Tasks by reading task details and attachments, posting milestone updates, attaching results, and setting accurate statuses. It also supports organizing subtasks, moving tasks between projects, and linking active work threads.

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

• Reviewing task details and attachments before starting
• Recording progress and attaching deliverables
• Updating review and completion statuses

Turn research about an existing app into a technical plan for a new implementation. Choose technologies, define database tables and access rules, map API routes, and order development around a small, complete core workflow.

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

• Choose technologies for an alternative app
• Design database tables, indexes, and access rules
• Map API routes and scheduled background jobs

Record daily follower counts and post engagement, then analyze growth rates and changes over time. Track how individual posts gain and lose attention, classify their patterns, and receive suggestions for future content.

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

• Recording daily follower counts and engagement
• Checking whether follower growth is accelerating
• Estimating when a follower milestone may be reached

Turn written instructions into infographics for statistics, comparisons, timelines, and more. Choose layouts and color palettes, optionally research supporting facts, and receive versioned images with automated quality reviews and refinement when scores fall below the chosen threshold.

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

• Turning survey results into a statistical infographic
• Creating a side-by-side product comparison
• Visualizing company history or project milestones

Archive accumulated phase directories from completed milestones

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

Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone

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

Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.

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

Add phase to end of current milestone in roadmap

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

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

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

Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻

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

Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.

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

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users sign up but dont stick around", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users quit after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

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

Write and distribute launch and publicity content across LinkedIn, X/Twitter, Instagram, Discord, Medium, Substack, and YouTube. Produces per-platform copy that does not read as AI-written (no em dashes, no "thrilled to announce", no engagement-bait), plus the exact image/video specs and character limits each platform wants. Use this skill whenever the user wants to announce, launch, publicize, promote, cross-post, or share anything - a product, a feature, an open-source release, a research paper, a blog post, a demo video, a milestone, a job opening, or a conference talk. Trigger it on phrases like "post this on LinkedIn", "write a launch tweet", "announce this", "share this in Discord", "turn this into a thread", "what should I post", "write a Medium article about", "help me with distribution", "draft a YouTube description", "make this sound less like AI", or "de-slop this post". Also use it when the user has just finished shipping something and asks how to get it in front of people.

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

Designs a translational blueprint for moving a biomedical finding toward diagnosis, prognosis, treatment response prediction, patient stratification, or therapeutic development, with explicit translational milestones, validation thresholds, and feasibility-sensitive route framing.

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