'brownfield' 검색 결과

Register and search existing Git repositories and worktrees, then choose which projects Ouroboros interviews use as context. You can also generate a configuration containing verified build, test, and other check commands for the evaluation workflow.

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

• Selecting existing projects as interview context
• Finding registered repositories by topic
• Rescanning after repositories are added or moved

Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts.

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

Drafts Brownfields Agreements for contaminated-property transactions under CERCLA, EPA brownfields programs, and state voluntary cleanup programs. Structures BFPP liability protections, All Appropriate Inquiries documentation, remediation obligations, institutional controls, cost allocation, and long-term stewardship covenants. Use when drafting brownfields purchase agreements, prospective purchaser agreements, voluntary cleanup MOAs, or environmental covenant frameworks.

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

Use when a task needs the judgment of a Brownfield Redevelopment Specialist and Site Manager — confirming landowner liability protections (BFPP/AAI) before a contaminated-site acquisition closes, matching a cleanup standard to the actual reuse plan instead of defaulting to the most conservative one, sequencing a brownfield funding stack (EPA grants, state VCP, tax credits) by eligibility dependency, or deciding whether an institutional control/deed restriction needs disclosure to a lender or buyer.

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

Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use eas-app-stores.

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

A 5-minute gate the coder runs at project kickoff (and again whenever the repo shape changes). Classifies the workspace into Greenfield / Brownfield-large / Mid-size-familiar / Library-SDK, then maps the state to an agent strategy (autonomy, context primitive, tool choice). Use BEFORE picking Cursor vs Claude Code vs Aider, BEFORE turning on repo-map, BEFORE writing the first prompt. Skip only if the same repo was gated within the last day and nothing changed. Search keywords: greenfield vs brownfield, new project vs existing codebase, project setup strategy, legacy codebase agent, where to start a coding agent.

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

Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".

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

Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR/XCFramework, or adding Expo to an existing Kotlin/Swift project. Covers both the isolated approach and the integrated approach.

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

기존 코드의 일부를 감사하고 설계 결정 기록, 구현 관행, 누락 기능, 기술 선택의 네 관점에서 문제를 정리합니다. 계획부터 테스트, 수정, 재감사까지 진행합니다.

• 인수한 코드를 검토할 때
• 개발 도중 ECC 절차를 도입할 때
• 기능 추가 전에 모듈을 재검토할 때

Audit an existing project's design documents and supporting files to check whether their formats work with the template's skills. Get a numbered migration plan that prioritizes gaps and required changes, rather than simply listing what exists.

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

• Checking existing documents before adopting a project template
• Auditing game design documents or architecture decision records
• Prioritizing gaps in project tracking and configuration files

Assess existing Google Cloud folders and projects through read-only discovery. Compare resource locations, service usage, and customer-managed encryption requirements with Assured Workloads frameworks, then report suitable options and policy readiness findings.

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

• Assess an existing folder or project's policy readiness
• Compare EU or US data boundary frameworks
• Review location, service, and encryption readiness

Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.

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

• Designing procedures for environments with varying conditions
• Resuming interrupted operations from verified evidence
• Deciding whether an agent or ordinary code should control a procedure

Analyze brownfield codebase and create initial continuity ledger

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

Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

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

Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.

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

Assesses whether and how an existing mobile product should migrate to React Native. Use when auditing one or more product repositories for migration readiness, including products whose iOS, Android, and other clients live in separate directories or repositories; choosing brownfield, greenfield, or a checkpoint-based path; defining a representative trial; or preparing a baseline and ROI decision before implementation. When product scope or material evidence is unavailable, grills the stakeholder with exactly one question per turn instead of sending a questionnaire.

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

将 CodeGraph 作为默认内置 MCP-backed 代码图谱能力接入，用于 brownfield 符号搜索、 调用链、影响面和上下文查询。输出必须回落到 `/team-*` 主链和 artifacts。

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

Use when onboarding to an unfamiliar codebase, before a major refactor, on a brownfield project before /gsd-new-project, or to refresh .planning/codebase/. Spawns up to 4 parallel mapper agents that write 7 documents.

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

Analyze brownfield codebase and create initial continuity ledger

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

Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

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

Mathematically rigorous Socratic interview system that drives ambiguity below 20% before any code is written. One question per message, weighted ambiguity scoring, brownfield-aware, outputs a complete PRD. Replaces discovery-interview with a stricter protocol.

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

Use when analyzing an existing TypeScript or JavaScript codebase to decide where and how to introduce Inngest. Covers repository discovery, framework and package detection, finding durability gaps in HTTP handlers, webhooks, cron jobs, queues, long-running jobs, AI agents, Agent Evals, polling loops, eval loops, and side-effect-heavy code, then producing and implementing an incremental integration plan.

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

Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.

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

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

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