Β§ PI Β· AGENTIC DISCIPLINE

Engineering discipline, with the agent wired in. μ—”μ§€λ‹ˆμ–΄λ§ λ””μ‚¬μ΄ν”Œλ¦°, μ—μ΄μ „νŠΈκ°€ λ‚΄μž₯된.

Strict engineering discipline and agentic orchestration for the pi coding agent. Multi-agent workflows, durable goals, and verifier-gated delivery. pi μ½”λ”© μ—μ΄μ „νŠΈλ₯Ό μœ„ν•œ μ—„κ²©ν•œ μ—”μ§€λ‹ˆμ–΄λ§ λ””μ‚¬μ΄ν”Œλ¦°κ³Ό μ—μ΄μ „νŠΈ μ˜€μΌ€μŠ€νŠΈλ ˆμ΄μ…˜. 닀쀑 μ—μ΄μ „νŠΈ μ›Œν¬ν”Œλ‘œ, μ§€μ†ν˜• λͺ©ν‘œ, 검증 기반 전달.

MIT License
ROACH PI
  ____   ___    _    ____ _   _   ____ ___
 |  _ \ / _ \  / \  / ___| | | | |  _ \_ _|
 | |_) | | | |/ _ \| |   | |_| | | |_) | |
 |  _ <| |_| / ___ \ |___|  _  | |  __/| |
 |_| \_\\___/_/   \_\____|_| |_| |_|  |___|

                  ROACH PI
      Durable Goals | Multi-Agent | Verifier-Gated
           /setup  /clarify  /goal  /loop
18+
Agents
MIT
License
100
Concurrent Jobs
EN / KR
Bilingual
Β§ 01 Β· WHY ROACH PI

Why ROACH PI? μ™œ ROACH PIμΈκ°€μš”?

●
Fully Open Source μ™„μ „ν•œ μ˜€ν”ˆμ†ŒμŠ€

Every line is on GitHub. No hidden prompts, no secret system instructions, no obfuscated behavior. Tools, event hooks, skill injections, and agent prompts are all plain TypeScript and Markdown.

λͺ¨λ“  μ½”λ“œκ°€ GitHub에 κ³΅κ°œλ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€. μˆ¨κ²¨μ§„ ν”„λ‘¬ν”„νŠΈ, λΉ„λ°€ μ‹œμŠ€ν…œ μ§€μ‹œμ–΄, λ‚œλ…ν™”λœ λ™μž‘ μ—†μŒ. 도ꡬ, 이벀트 ν›…, μŠ€ν‚¬ μ£Όμž…, μ—μ΄μ „νŠΈ ν”„λ‘¬ν”„νŠΈκ°€ λͺ¨λ‘ 일반 TypeScript와 Markdown으둜 μž‘μ„±λ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€.

β˜…
Observable μ˜΅μ €λ²„λΉŒλ¦¬ν‹°

The footer displays real-time metrics every session: prompt cache hit rate, context usage bar, active tools, branch, and model. See exactly how your context is being utilized.

푸터에 λ§€ μ„Έμ…˜ μ‹€μ‹œκ°„ λ©”νŠΈλ¦­μ΄ ν‘œμ‹œλ©λ‹ˆλ‹€: ν”„λ‘¬ν”„νŠΈ μΊμ‹œ 적쀑λ₯ , μ»¨ν…μŠ€νŠΈ μ‚¬μš©λŸ‰ λ°”, ν™œμ„± 도ꡬ, 브랜치, λͺ¨λΈ. μ»¨ν…μŠ€νŠΈκ°€ μ–΄λ–»κ²Œ μ‚¬μš©λ˜λŠ”μ§€ μ •ν™•νžˆ ν™•μΈν•˜μ„Έμš”.

β– 
Transparent by Design λ””μžμΈλΆ€ν„° 투λͺ…ν•˜κ²Œ

No magic. Read the source and see exactly what the agent does. Skill rules are plain Markdown. Agent prompts are plain text. Every event hook is auditable.

λ§ˆλ²• μ—†μŒ. μ†ŒμŠ€λ₯Ό 읽고 μ—μ΄μ „νŠΈκ°€ μ •ν™•νžˆ 무엇을 ν•˜λŠ”μ§€ ν™•μΈν•˜μ„Έμš”. μŠ€ν‚¬ κ·œμΉ™μ€ 일반 Markdown, μ—μ΄μ „νŠΈ ν”„λ‘¬ν”„νŠΈλŠ” 일반 ν…μŠ€νŠΈ, λͺ¨λ“  이벀트 훅이 감사 κ°€λŠ₯ν•©λ‹ˆλ‹€.

β–Ά
Simple Over Clever 화렀함보닀 λ‹¨μˆœν•¨

We prefer straightforward solutions over elaborate orchestration. Fewer moving parts, fewer failure modes. See our contributing guidelines.

λ³΅μž‘ν•œ μ˜€μΌ€μŠ€νŠΈλ ˆμ΄μ…˜λ³΄λ‹€ λ‹¨μˆœν•œ 해결책을 μ„ ν˜Έν•©λ‹ˆλ‹€. μ›€μ§μ΄λŠ” 뢀뢄이 μ μ„μˆ˜λ‘ μ‹€νŒ¨λ„ μ μŠ΅λ‹ˆλ‹€. κΈ°μ—¬ κ°€μ΄λ“œλΌμΈμ„ μ°Έμ‘°ν•˜μ„Έμš”.

Β§ 02 Β· QUICK START

Quick Start λΉ λ₯Έ μ‹œμž‘

The extension provides a streamlined workflow: clarify β†’ goal. /goal creates, activates, continues, and verifies automatically.

μ΅μŠ€ν…μ…˜μ€ λ‹¨μˆœν•œ μ›Œν¬ν”Œλ‘œλ₯Ό μ œκ³΅ν•©λ‹ˆλ‹€: λͺ…ν™•ν™” β†’ goal. /goal이 μžλ™μœΌλ‘œ 생성, ν™œμ„±ν™”, 이어가기, 검증을 μ§„ν–‰ν•©λ‹ˆλ‹€.

Executable Workflow Video Executable Workflow Video

Live-style runtime preview showing command execution order, verifier gates, and evidence checkpoints.

Live-style runtime preview showing command execution order, verifier gates, and evidence checkpoints.

Recorded terminal workflow showing command execution order, evidence receipts, checkpoint updates, and verifier pass status.

  1. 00:05 done

    /setup bootstraps defaults and applies quiet startup settings.

  2. 00:28 done

    /clarify resolves ambiguity and emits the Goal Contract.

  3. 00:53 done

    /goal starts durable execution and tracks evidence receipts.

  4. 01:24 done

    /goal subgoal queues dependency-bound work packets.

  5. 02:15 verifying

    /loop schedules recurring checks while verifier waits for PASS.

Transcript Transcript

00:05 /setup -> bootstrap complete. 00:28 /clarify -> goal contract locked. 00:53 /goal -> runtime active. 01:24 /goal subgoal -> queue accepted. 02:15 /loop -> verifier PASS pending.

00:05 /setup -> bootstrap complete. 00:28 /clarify -> goal contract locked. 00:53 /goal -> runtime active. 01:24 /goal subgoal -> queue accepted. 02:15 /loop -> verifier PASS pending.

  1. 01

    /setup β€” Configure Settings β€” μ„€μ • ꡬ성

    Run once after installation to apply recommended settings. Sets quietStartup: true so the extension's custom ROACH PI banner replaces the default startup listing.

    μ„€μΉ˜ ν›„ ν•œ 번 μ‹€ν–‰ν•˜μ—¬ ꢌμž₯ 섀정을 μ μš©ν•©λ‹ˆλ‹€. μ΅μŠ€ν…μ…˜μ˜ μ»€μŠ€ν…€ ROACH PI λ°°λ„ˆκ°€ κΈ°λ³Έ μ‹œμž‘ λͺ©λ‘μ„ λŒ€μ²΄ν•˜λ„λ‘ quietStartup: trueλ₯Ό μ„€μ •ν•©λ‹ˆλ‹€.

  2. 02

    /clarify β€” Resolve Ambiguity β€” λͺ¨ν˜Έμ„± ν•΄κ²°

    The agent asks dynamic, context-aware questions one at a time, using codebase exploration only when implementation or uncertain technical context makes it necessary. Ends with a structured Goal Contract that defines scope, constraints, success criteria, and evidence requirements.

    μ—μ΄μ „νŠΈκ°€ 동적이고 λ¬Έλ§₯에 λ§žλŠ” μ§ˆλ¬Έμ„ ν•˜λ‚˜μ”© 묻고, κ΅¬ν˜„μ΄λ‚˜ λΆˆν™•μ‹€ν•œ 기술 λ§₯락 λ•Œλ¬Έμ— ν•„μš”ν•  λ•Œλ§Œ μ½”λ“œλ² μ΄μŠ€λ₯Ό νƒμƒ‰ν•©λ‹ˆλ‹€. λ²”μœ„, μ œμ•½, 성곡 κΈ°μ€€, 증거 μš”κ΅¬μ‚¬ν•­μ„ μ •μ˜ν•˜λŠ” κ΅¬μ‘°ν™”λœ Goal Contract둜 λλ‚©λ‹ˆλ‹€.

  3. 03

    /goal β€” Activate Durable Execution β€” durable μ‹€ν–‰ ν™œμ„±ν™”

    Starts or continues a durable runtime that tracks goals, subgoals, todos, evidence, blockers, verifier receipts, and automatic continuation. Completion requires an independent verifier PASS.

    λͺ©ν‘œ, ν•˜μœ„ λͺ©ν‘œ, todo, 증거, 차단 μš”μ†Œ, 검증 영수증, μžλ™ 이어가기λ₯Ό μΆ”μ ν•˜λŠ” durable runtime을 μ‹œμž‘ν•˜κ±°λ‚˜ μ΄μ–΄κ°‘λ‹ˆλ‹€. μ™„λ£Œμ—λŠ” 독립 verifier PASSκ°€ ν•„μš”ν•©λ‹ˆλ‹€.

  4. 04

    /goal subgoal β€” Subgoal Queueing β€” ν•˜μœ„ λͺ©ν‘œ νμž‰

    For complex multi-step tasks. Queue subgoals with dependencies and required evidence, then let the goal runtime advance after verifier-guarded completion.

    λ³΅μž‘ν•œ 닀단계 μž‘μ—…μ„ μœ„ν•΄. μ˜μ‘΄μ„±κ³Ό ν•„μš”ν•œ 증거가 μžˆλŠ” ν•˜μœ„ λͺ©ν‘œλ₯Ό 큐에 λ„£κ³ , verifier-guarded μ™„λ£Œ ν›„ goal runtime이 μ§„ν–‰ν•˜κ²Œ ν•©λ‹ˆλ‹€.

  5. 05

    /loop β€” Session Loop Scheduler β€” μ„Έμ…˜ 루프 μŠ€μΌ€μ€„λŸ¬

    Schedule recurring prompts at fixed intervals. Cron-style timing β€” fires on schedule regardless of execution state. Supports 5s, 10m, 2h, 1d formats. Up to 100 concurrent jobs with per-job error isolation and automatic cleanup on session shutdown.

    κ³ μ • κ°„κ²©μœΌλ‘œ 반볡 ν”„λ‘¬ν”„νŠΈλ₯Ό μŠ€μΌ€μ€„λ§ν•©λ‹ˆλ‹€. Cron μŠ€νƒ€μΌ 타이밍 β€” μ‹€ν–‰ μƒνƒœμ™€ 관계없이 μŠ€μΌ€μ€„λŒ€λ‘œ μ‹€ν–‰λ©λ‹ˆλ‹€. 5s, 10m, 2h, 1d ν˜•μ‹μ„ μ§€μ›ν•©λ‹ˆλ‹€. μ΅œλŒ€ 100개 λ™μ‹œ μž‘μ—…, μž‘μ—…λ³„ μ—λŸ¬ 격리, μ„Έμ…˜ μ’…λ£Œ μ‹œ μžλ™ 정리.

πŸ’‘ Tip: The ask_user_question tool is always available β€” the agent will ask clarifying questions autonomously whenever it detects ambiguity, even outside /clarify mode.

πŸ’‘ 팁: ask_user_question λ„κ΅¬λŠ” 항상 μ‚¬μš© κ°€λŠ₯ν•©λ‹ˆλ‹€ β€” /clarify λͺ¨λ“œ μ™Έμ—μ„œλ„ λͺ¨ν˜Έμ„±μ„ κ°μ§€ν•˜λ©΄ μžλ™μœΌλ‘œ μ§ˆλ¬Έν•©λ‹ˆλ‹€.

Β§ 03 Β· KEY FEATURES

Key Features μ£Όμš” κΈ°λŠ₯

Bundled Agents 18+
Parallel Tasks 12 / 10
Chain Depth 3 max
Loop Jobs 100
β˜…
Multi-Agent Orchestration 닀쀑 μ—μ΄μ „νŠΈ μ˜€μΌ€μŠ€νŠΈλ ˆμ΄μ…˜

18+ bundled agents for exploration, execution, planning, and review. Delegate tasks via single, parallel (max 12 tasks, 10 concurrent), or chain modes with cycle detection and depth guards.

탐색, μ‹€ν–‰, κ³„νš, 리뷰λ₯Ό μœ„ν•œ 18개 μ΄μƒμ˜ λ²ˆλ“€ μ—μ΄μ „νŠΈ. 사이클 감지 및 깊이 κ°€λ“œμ™€ ν•¨κ»˜ 단일, 병렬(μ΅œλŒ€ 12개 μž‘μ—…, 10개 λ™μ‹œ), 체인 λͺ¨λ“œλ‘œ μž‘μ—…μ„ μœ„μž„ν•˜μ„Έμš”.

●
Engineering Discipline μ—”μ§€λ‹ˆμ–΄λ§ λ””μ‚¬μ΄ν”Œλ¦°

Karpathy rules are auto-injected into code-writing agents so implementation stays surgical, evidence-based, and scoped to the active goal.

Karpathy κ·œμΉ™μ΄ μ½”λ“œ μž‘μ„± μ—μ΄μ „νŠΈμ— μžλ™ μ£Όμž…λ˜μ–΄ κ΅¬ν˜„μ΄ ν™œμ„± λͺ©ν‘œ λ²”μœ„ μ•ˆμ—μ„œ 외과적이고 증거 기반으둜 μœ μ§€λ©λ‹ˆλ‹€.

β– 
Goal Runtime Pipeline λͺ©ν‘œ λŸ°νƒ€μž„ νŒŒμ΄ν”„λΌμΈ

/goal tracks active subgoals, evidence, blockers, and verifier receipts. Completion only lands after reviewer-verifier independently returns PASS.

/goal은 ν™œμ„± ν•˜μœ„ λͺ©ν‘œ, 증거, 차단 μš”μ†Œ, 검증 μ˜μˆ˜μ¦μ„ μΆ”μ ν•©λ‹ˆλ‹€. μ™„λ£ŒλŠ” reviewer-verifierκ°€ λ…λ¦½μ μœΌλ‘œ PASSλ₯Ό λ°˜ν™˜ν•œ λ’€μ—λ§Œ ν™•μ •λ©λ‹ˆλ‹€.

β–Ά
TUI Customization TUI μ»€μŠ€ν„°λ§ˆμ΄μ œμ΄μ…˜

Custom ROACH PI ASCII banner, branded footer with directory, branch, model, context bar, cache hit rate, and active tools display.

디렉토리, 브랜치, λͺ¨λΈ, μ»¨ν…μŠ€νŠΈ λ°”, μΊμ‹œ 적쀑λ₯ , ν™œμ„± 도ꡬ ν‘œμ‹œκ°€ μžˆλŠ” μ»€μŠ€ν…€ ROACH PI ASCII λ°°λ„ˆ 및 λΈŒλžœλ””λ“œ ν‘Έν„°.

●
Context Management μ»¨ν…μŠ€νŠΈ 관리

Microcompaction truncates old tool results. Phase-aware summarization preserves workflow state across compaction. Phase and goal document survive context limits.

λ§ˆμ΄ν¬λ‘œμ»΄νŒ©μ…˜μ΄ 였래된 도ꡬ κ²°κ³Όλ₯Ό μžλ¦…λ‹ˆλ‹€. 단계 인식 μš”μ•½μ΄ μ»΄νŒ©μ…˜ μ „λ°˜μ— 걸쳐 μ›Œν¬ν”Œλ‘œ μƒνƒœλ₯Ό λ³΄μ‘΄ν•©λ‹ˆλ‹€. 단계 및 λͺ©ν‘œ λ¬Έμ„œκ°€ μ»¨ν…μŠ€νŠΈ ν•œκ³„λ₯Ό μ΄ˆκ³Όν•©λ‹ˆλ‹€.

β–Ά
Session Loop Scheduler μ„Έμ…˜ 루프 μŠ€μΌ€μ€„λŸ¬

Schedule recurring prompts with /loop 5m check status. Cron-style fixed intervals, per-job error isolation, AbortController cancellation, timeout protection, and automatic cleanup on session shutdown. Up to 100 concurrent jobs.

/loop 5m check status둜 반볡 ν”„λ‘¬ν”„νŠΈλ₯Ό μŠ€μΌ€μ€„λ§ν•©λ‹ˆλ‹€. Cron μŠ€νƒ€μΌ κ³ μ • 간격, μž‘μ—…λ³„ μ—λŸ¬ 격리, AbortController μ·¨μ†Œ, νƒ€μž„μ•„μ›ƒ 보호, μ„Έμ…˜ μ’…λ£Œ μ‹œ μžλ™ 정리. μ΅œλŒ€ 100개 λ™μ‹œ μž‘μ—….

β˜…
Behavioral Skills 행동 μŠ€ν‚¬

Bundled LLM skill rulesets: clarification, durable goal execution, verifier-guarded review, simplify, systematic debugging, Karpathy discipline, Rob Pike optimization, and more.

λ²ˆλ“€ LLM μŠ€ν‚¬ λ£°μ…‹: λͺ…ν™•ν™”, durable goal μ‹€ν–‰, verifier-guarded 리뷰, λ‹¨μˆœν™”, 체계적 디버깅, Karpathy λ””μ‚¬μ΄ν”Œλ¦°, Rob Pike μ΅œμ ν™” λ“±.

β—†
FFF Search Engine FFF 검색 μ—”μ§„

Built-in search acceleration for find and grep through a native FFF engine. Adds multi_grep, frecency-aware ranking, git-aware indexing, optional replacement of @ file autocomplete, and built-in fallback to standard find/grep behavior when the native layer is unavailable.

λ„€μ΄ν‹°λΈŒ FFF 엔진을 ν†΅ν•œ find / grep λ‚΄μž₯ 검색 가속. multi_grep, frecency 기반 λž­ν‚Ή, git 인식 인덱싱, 선택적 @ 파일 μžλ™μ™„μ„±μ„ μΆ”κ°€ν•˜λ©°, λ„€μ΄ν‹°λΈŒ λ ˆμ΄μ–΄λ₯Ό μ“Έ 수 없을 λ•ŒλŠ” κΈ°λ³Έ find/grep λ™μž‘μœΌλ‘œ ν΄λ°±ν•©λ‹ˆλ‹€.

Β§ 04 Β· FAQ

FAQ

What is the pi coding agent? pi μ½”λ”© μ—μ΄μ „νŠΈλž€ λ¬΄μ—‡μΈκ°€μš”?

pi is a terminal-based AI coding agent that helps you read, write, and debug code directly from your terminal. It supports extensions, custom tools, themes, and multiple AI providers. GitHub β†’

piλŠ” ν„°λ―Έλ„μ—μ„œ 직접 μ½”λ“œλ₯Ό 읽고, μ“°κ³ , λ””λ²„κΉ…ν•˜λŠ” 터미널 기반 AI μ½”λ”© μ—μ΄μ „νŠΈμž…λ‹ˆλ‹€. μ΅μŠ€ν…μ…˜, μ»€μŠ€ν…€ 도ꡬ, ν…Œλ§ˆ 및 μ—¬λŸ¬ AI ν”„λ‘œλ°”μ΄λ”λ₯Ό μ§€μ›ν•©λ‹ˆλ‹€. GitHub β†’

Do I need to install the engineering-discipline skills separately? μ—”μ§€λ‹ˆμ–΄λ§ λ””μ‚¬μ΄ν”Œλ¦° μŠ€ν‚¬μ„ λ³„λ„λ‘œ μ„€μΉ˜ν•΄μ•Ό ν•˜λ‚˜μš”?

No. All engineering discipline skills are bundled with this extension. Just install the extension and run /setup β€” everything is ready out of the box.

μ•„λ‹ˆμš”. λͺ¨λ“  μ—”μ§€λ‹ˆμ–΄λ§ λ””μ‚¬μ΄ν”Œλ¦° μŠ€ν‚¬μ΄ 이 μ΅μŠ€ν…μ…˜μ— λ²ˆλ“€λ‘œ ν¬ν•¨λ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€. μ΅μŠ€ν…μ…˜μ„ μ„€μΉ˜ν•˜κ³  /setup을 μ‹€ν–‰ν•˜μ„Έμš” β€” λͺ¨λ“  것이 μ¦‰μ‹œ μ‚¬μš© κ°€λŠ₯ν•©λ‹ˆλ‹€.

How do the subagent modes work? μ„œλΈŒμ—μ΄μ „νŠΈ λͺ¨λ“œλŠ” μ–΄λ–»κ²Œ μž‘λ™ν•˜λ‚˜μš”?

Single: One-off tasks sent to a specific agent.
Parallel: Dispatch multiple agents at once (max 12 tasks, 10 concurrent). Each runs independently.
Chain: Sequential pipeline where each step receives the previous step's output via {previous} placeholder.
All modes include cycle detection, depth limits (max 3), and concurrency control.

단일: νŠΉμ • μ—μ΄μ „νŠΈμ— λ³΄λ‚΄λŠ” μΌνšŒμ„± μž‘μ—….
병렬: μ—¬λŸ¬ μ—μ΄μ „νŠΈλ₯Ό ν•œ λ²ˆμ— λ””μŠ€νŒ¨μΉ˜(μ΅œλŒ€ 12개 μž‘μ—…, 10개 λ™μ‹œ). 각각 λ…λ¦½μ μœΌλ‘œ μ‹€ν–‰.
체인: 각 단계가 이전 λ‹¨κ³„μ˜ 좜λ ₯을 {previous} ν”Œλ ˆμ΄μŠ€ν™€λ”λ‘œ λ°›λŠ” 순차 νŒŒμ΄ν”„λΌμΈ.
λͺ¨λ“  λͺ¨λ“œμ— 사이클 감지, 깊이 μ œν•œ(μ΅œλŒ€ 3), λ™μ‹œμ„± μ œμ–΄κ°€ ν¬ν•¨λ©λ‹ˆλ‹€.

How does engineering discipline stay enforced? μ—”μ§€λ‹ˆμ–΄λ§ λ””μ‚¬μ΄ν”Œλ¦°μ€ μ–΄λ–»κ²Œ μœ μ§€λ˜λ‚˜μš”?

The harness injects focused implementation guardrails into code-writing agents: read before writing, keep changes scoped, verify assumptions, and record evidence before completion.

ν•˜λ„€μŠ€λŠ” μ½”λ“œ μž‘μ„± μ—μ΄μ „νŠΈμ— μ§‘μ€‘λœ κ΅¬ν˜„ κ°€λ“œλ ˆμΌμ„ μ£Όμž…ν•©λ‹ˆλ‹€. μ“°κΈ° 전에 읽고, λ³€κ²½ λ²”μœ„λ₯Ό μ§€ν‚€λ©°, 가정을 κ²€μ¦ν•˜κ³ , μ™„λ£Œ 전에 증거λ₯Ό κΈ°λ‘ν•©λ‹ˆλ‹€.

How does the FFF search engine change my workflow? FFF 검색 엔진은 μ›Œν¬ν”Œλ‘œλ₯Ό μ–΄λ–»κ²Œ λ°”κΎΈλ‚˜μš”?

It overrides the built-in find and grep tools with a native FFF-backed implementation and adds multi_grep. In both mode it also replaces @ file autocomplete suggestions. Use /fff-health to inspect engine status and /fff-mode tools-only if you only want the tool overrides.

κΈ°λ³Έ find / grep 도ꡬλ₯Ό λ„€μ΄ν‹°λΈŒ FFF 기반 κ΅¬ν˜„μœΌλ‘œ κ΅μ²΄ν•˜κ³  multi_grepλ₯Ό μΆ”κ°€ν•©λ‹ˆλ‹€. both λͺ¨λ“œμ—μ„œλŠ” @ 파일 μžλ™μ™„μ„±λ„ λŒ€μ²΄ν•©λ‹ˆλ‹€. μ—”μ§„ μƒνƒœλŠ” /fff-health둜 ν™•μΈν•˜κ³ , 도ꡬ override만 μ›ν•˜λ©΄ /fff-mode tools-onlyλ₯Ό μ‚¬μš©ν•˜μ„Έμš”.

How do I handle complex multi-step goals? λ³΅μž‘ν•œ 닀단계 λͺ©ν‘œλŠ” μ–΄λ–»κ²Œ μ²˜λ¦¬ν•˜λ‚˜μš”?

Use /clarify to produce a Goal Contract, then /goal to create the durable runtime entry. Add subgoals when the work needs decomposition.

/clarify둜 Goal Contractλ₯Ό λ§Œλ“  λ‹€μŒ /goal둜 durable runtime ν•­λͺ©μ„ λ§Œλ“œμ„Έμš”. μž‘μ—… λΆ„ν•΄κ°€ ν•„μš”ν•˜λ©΄ ν•˜μœ„ λͺ©ν‘œλ₯Ό μΆ”κ°€ν•˜μ„Έμš”.