'milestone' 검색 결과

Project state awareness and session recovery for GSD-managed projects. Use this skill whenever: starting a new work session, resuming after a break, the user asks "where did we leave off" or "what's the current state", before making substantial code changes (to check for existing plans), the user seems disoriented about project status, or when something seems off and STATE.md might have relevant context. Also activates when the user references .planning/ files, milestones, phases, or project progress.

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

Use when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing an item without completion under a required reason (duplicate, out of scope, superseded, wontfix, blocked), marking an item done with an evidence trail and required summary, or initializing GitHub tracking infrastructure for a project. Stops when the item already has a plan or is blocked on missing information.

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

Routes to the correct dh skill entry point by intent. Use when unsure which development-harness skill to invoke, starting a development workflow, or invoking /dh directly. Covers capture, groom, plan, execute, single task, quality gates, and milestone routing.

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

Install and configure the GitHub CLI (gh) for AI agent environments where gh may not be pre-installed and git remotes use local proxies instead of github.com. Use when gh command not found, shutil.which returns None, need GitHub API access for issues or PRs or releases or workflow runs, or repository operations fail with 'failed to determine base repo' error. Provides auto-install script with SHA256 verification, GITHUB_TOKEN auth with anonymous fallback, and the required -R flag pattern for proxy environments. Covers project management via GitHub Projects V2, milestones via REST API, issue lifecycle templates, and label taxonomy management.

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

Run the Anabasis v2 improvement loop: score the five points, read each campaign at its milestone, find the link that holds its next promotion, fix that link's owner, prove the path, record a prediction, launch fresh, watch, read and decide. Use when the operator asks to keep campaigns going, run a pass or an hourly audit, read a promotion, investigate a campaign that is not promoting, or choose the next run. Owns the experiment and its evidence; AGENTS.md section 3 owns the operator's decisions.

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

Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.

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

设计里程碑和交付门禁时使用。适用于阶段评审、上线前检查、重要节点验收。优先使用 Stage-Gate 方法 + 验收标准 + 强制门禁清单。

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

Autonomously work a `.pm` workstream to completion — pick the next pending milestone, implement every task end to end, /ship it, then move to the next until none remain. Use when the user asks to "loop", drain, or work through a whole workstream's backlog (e.g. `/loop-worker w1`). Sequential, not interval-based; for a timed poll use /loop.

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

Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.

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

Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.

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

Coordinates fundraising execution with PPM preparation, DDQ completion, legal documentation, and closing mechanics. Use when managing fund launches, coordinating formation processes, or tracking fundraising milestones.

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

Structures IPO execution from organizational meeting through pricing with workstream coordination and timeline management. Use when managing IPOs, coordinating offering processes, or tracking ECM execution milestones.

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

Use when one milestone is too large for a single specification or plan and must ship as several ordered stages across sessions.

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

Draft a project charter that defines scope, stakeholders, success criteria, and initial risk register. Covers problem statement, RACI matrix, milestone planning, and scope boundaries for both agile and classic methodologies. Use when kicking off a new project or initiative, formalizing scope after an informal start, aligning stakeholders before detailed planning begins, or transitioning from discovery to active project work.

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

Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.

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

Review execution against the frozen Execution Contract, produce Evidence/Gaps, and decide pass or unfreeze. Use after ac-execute or at milestone acceptance gates.

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

Use when asked to review learning progress after a milestone. Not for engineering retrospectives, use engineering-retrospective. For agent-environment ones, use agent-environment-retrospective.

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

Use when asked to create a multi-session learning plan. Returns a milestoned plan, practice, and review rubric. Don't use for tasks that require source or remote-system changes.

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

Use when a user requests an engineering retrospective for a period. Not for agent-environment retrospectives: use agent-environment-retrospective. For learning milestones: use learning-retrospective.

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

Audit one bounded Proto UI collaboration-governance slice and route policy-determined drift toward reversible correction. Use across Issues, pull requests, Discussions, labels, milestones, Project, rules, permissions, or Actions. This evidence leaf is read-only; authorized corrections continue in their registered leaves.

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

30/60/90 Day Onboarding Plan — Day 1 setup, week 1 ramp, month 1 milestones, month 2 contributions, month 3 evaluation criteria

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

Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mentions like 'how do I get my users to spread the word' or 'can users invite others' should trigger this. Includes anti-fraud measures and copy templates for both referrer and referee. Use this whenever user-driven acquisition or viral mechanics are discussed.

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

Distinguishing aims, objectives, hypotheses, and milestones — the hierarchy that keeps proposals logically tight.

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

Break the spell of local productivity. Ask whether completing all open beads actually closes the gap to the project goal. Use at milestones or when busy agents feel directionally off.

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