'plans' 검색 결과

Close a completed development milestone by checking finished work, summarizing achievements, and archiving plans and requirements. Update project records and create a Git version tag to prepare for the next milestone.

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

• Archive plans and requirements for a completed version
• Summarize milestone achievements and change statistics
• Update project records before the next milestone

Check the `.planning/` directory for missing files, invalid settings, inconsistent state, and orphaned plans. Report issues to address, optionally request repairs, or check context usage—the share of the session’s text capacity already used.

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

• Checking planning files for missing content or inconsistencies
• Finding orphaned plans
• Requesting repairs after a planning directory check

Route project management requests to the appropriate GSD skill. Use it to start projects, onboard existing code, manage milestones, import plans, or review backlog items without choosing the individual skill yourself.

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

• Start a project or onboard an existing codebase
• Create or complete a development milestone
• Audit a milestone or summarize its status

Store phase documents verbatim in MemPalace, organized as decisions, plans, or milestones. Avoid duplicate entries and mirror decision or delivery facts into a knowledge graph that records when those facts became valid.

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

• Preserve decision documents with their source information
• File plans and summaries by document type
• Record dated decision and delivery facts in a knowledge graph

Create distinct paid advertising concepts, headlines, copy, and production briefs from validated brand information and campaign goals. Each concept connects its message to evidence, audience needs, platform requirements, and a hypothesis to test.

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

• Develop campaign concepts with distinct strategic angles
• Draft ad headlines and descriptions
• Prepare creative briefs and production plans

Use Plannotator to review plans, code changes, documents, and running local apps in a browser. This reference covers returning feedback to agents, browsing past decisions, sharing guided code reviews, and leaving questions for later replies.

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

• Reviewing and approving plans or specifications
• Reviewing local code changes or pull requests
• Annotating documents or running local apps

Organize product requirements into a single-page document covering the problem, success metrics, scope, user scenarios, design notes, rollout plans, and open questions. A status label shows whether the specification is a draft, approved, or shipped.

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

• Drafting requirements for a new product feature
• Defining success metrics and scope
• Documenting user scenarios and design notes

Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.

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

• Define feature requirements and scope in a PRD
• Split development plans into tasks and sync them to GitHub
• Coordinate parallel agents working on issues

Create medical visit notes in SOAP format, which separates patient reports, observed findings, clinical assessment, and care plans. Organize the available information into a complete Markdown or plain text file written in one operation.

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

• Organizing patient visit information into SOAP notes
• Documenting symptoms, medical history, and examination findings
• Recording treatment plans and follow-up arrangements

Organize patient and visit information into a SOAP note, a medical record covering symptoms, findings, assessment, and care plans. Save the complete note in one file and flag missing information.

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

• Organizing visit details into a SOAP note
• Combining symptoms, findings, and care plans in one file
• Checking documentation for missing information

Compare a previous PESTEL analysis of political, economic, social, technological, environmental, and legal factors with current evidence. Identify meaningful changes and broken assumptions, then summarize their implications for strategy and product plans with sources.

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

• Quarterly reviews of external business conditions
• Checking assumptions after regulatory changes
• Connecting external changes to product plans

Design key performance indicators for business or product decisions, including definitions, calculations, targets, and measurement plans. Select supporting metrics that explain progress and guardrails that track unwanted effects on quality, cost, or other outcomes.

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

• Define success metrics for a product launch
• Choose growth metrics and supporting drivers
• Set an experiment's success metric and guardrails

Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.

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

• Planning a gradual replacement of a legacy system
• Comparing service separation and consolidation strategies
• Preparing a language or framework migration

Stress-test an idea, plan, or proposal through focused critique. The skill examines assumptions, opposing arguments, failure scenarios, attacks, or evidence, then uses your responses to refine the position and identify unresolved trade-offs and risky assumptions.

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

• Checking a proposal's assumptions before committing
• Anticipating how a project could fail
• Testing whether evidence supports a conclusion

Create new Feishu cloud documents from Markdown, a text format for structured content. Choose a folder or knowledge library location, and include tables, images, and diagrams in meeting notes or project plans.

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

• Create meeting notes in a specified folder
• Write project plans with tables and diagrams
• Add technical documents under a knowledge library page

Clean up DeepChat's specification-driven development documents after implementation and validation. Review feature, issue, and architecture files, remove completed or obsolete material when evidence supports deletion, and preserve maintained specifications while checking references.

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

• Remove issue documents after confirming a bug is resolved
• Clear old plans from completed feature work
• Update or remove architecture documents after replacement

Guide a development task through requirements research, solution comparison, planning, implementation, optimization, and review. The workflow asks for approval at key stages and saves plans and completed task records in the project.

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

• Clarifying requirements before development
• Comparing alternative implementation approaches
• Reviewing a detailed plan before coding

Organize research knowledge by project in Obsidian, from creating folder structures and routing notes to maintaining daily logs, plans, and indexes. It also manages note changes and coordinates checks for broken links and registry consistency.

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

• Setting up an Obsidian workspace for a research project
• Organizing sources, research notes, and experiment results
• Updating daily logs, project plans, and indexes

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

Turn a research task or estimation problem into a saved implementation plan grounded in project code, prior decisions, and relevant methods. Adjust the detail to the task and document dependencies, risks, diagnostics, and acceptance criteria.

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

• Planning implementation of a new estimation method
• Planning fixes for convergence or data problems
• Organizing robustness checks and replication steps

Investigate slow PostgreSQL and MySQL queries using execution plans, which show how queries run, and performance measurements. Develop index changes, SQL rewrites, and configuration adjustments, then validate their effects with measurements and monitoring.

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

• Investigating the causes of slow queries
• Reviewing database index design
• Tuning PostgreSQL or MySQL configuration

Turn a text development plan into a visual document with diagrams, file maps, annotated code, and open questions. For interface work, add wireframes or an interactive prototype so reviewers can examine screens and behavior before implementation.

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

• Turn an existing text plan into a visual review document
• Compare interface states and user flows before coding
• Explain architecture and data flow with inline diagrams

Turn a multi-step feature into an implementation plan that another engineer can follow without prior context. The plan includes exact file paths, complete code, test commands, expected results, and small, verifiable steps.

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

• Planning a feature with multiple implementation steps
• Handing development work to another engineer or agent
• Breaking a complex refactor into verifiable tasks

Review plans, designs, or code by imagining how they could fail. Checks potential risks against surrounding context and existing safeguards, separates verified threats from false alarms, and helps decide whether to mitigate or accept them.

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

• Checking a plan for risks before implementation
• Reviewing risks in a pull request
• Finding gaps in dependency handling and rollback plans