You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The `.gemini/commands/` directory defines specialized workflows that automate ev
58
58
59
59
### 🔍 Phase 1: Planning & Discovery
60
60
***`/research <topic>`**: A deep, 3-phase investigation (Planning -> Data Gathering -> Reporting) that produces exhaustive Markdown reports in the `research/` directory. **Crucial for gathering technical requirements and state-of-the-art context.**
61
-
***`/learn <topic>`**: A grounded learning lifecycle (Audit -> Strategic Mapping -> Execution -> Codification) for mastering new technologies and building a permanent, machine-readable knowledge base in `.gemini/skills/`.
61
+
***`/learn <topic>`**: A grounded learning lifecycle (Audit -> Strategic Mapping -> Execution -> Codification) for mastering new technologies and building a permanent, machine-readable knowledge base in `.gemini/skills/` using the specialized `learner` subagent.
62
62
***`/plan`**: The **Architectural Bridge**. This interactive workflow translates ideas into actionable execution plans:
63
63
***Phase 1 (Clarification):** The agent interviews you to resolve ambiguities before planning.
64
64
***Phase 2 (Agentic Analysis):** A specialized `planner` subagent scans the codebase and generates a detailed technical strategy.
Copy file name to clipboardExpand all lines: docs/user-guide.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The most critical phase of any project occurs before you write a single line of
26
26
27
27
Your primary tool for forensic, scientific investigation.
28
28
29
-
-**How it works:** When a bug is detected, the `/debug` command implements a principled approach to problem-solving. It moves through four distinct phases: Context Analysis, Hypothesis Formulation, Isolated Testing on a temporary branch (`debug/hyp-*`), and finally a Synthesis of the findings into a **Root Cause Analysis (RCA)** report.
29
+
-**How it works:** When a bug is detected, the `/debug` command implements a principled approach to problem-solving using the specialized `debugger` subagent. It moves through four distinct phases: Context Analysis, Hypothesis Formulation, Isolated Testing on a temporary branch (`debug/hyp-*`), and finally a Synthesis of the findings into a **Root Cause Analysis (RCA)** report.
30
30
-**Why it works:** It forces the agent to identify the root cause *before* attempting a fix, preventing "guess-and-check" coding that can lead to regressions.
31
31
32
32
### `/plan`
@@ -40,13 +40,18 @@ Your tool for internal strategy and architectural design.
40
40
41
41
Your tool for mastering new technologies and codifying them into project skills.
42
42
43
-
-**How it works:** Implements a "Grounded Learning" philosophy through a 4-phase lifecycle:
43
+
-**How it works:** Implements a "Grounded Learning" philosophy through a 4-phase lifecycle using the `learner` subagent:
44
44
1.**Environment Audit:** Automatically detects if the library is already installed or has local integration points.
45
-
2.**Strategic Mapping:** Researches the topic and defines 3-5 granular Learning Objectives (the "Learning Map"). **Requires user approval via `ask_user`.**
46
-
3.**Grounded Execution:** The specialized `learner` sub-agent performs real-world experiments (writing and running scripts) to verify "gotchas," performance, and idiomatic patterns.
47
-
4.**Skill Codification:** Consolidates all findings into a permanent project skill in `.gemini/skills/<name>/`, including a mandatory `SKILL.md` file and reference documents.
45
+
...
48
46
-**Why it works:** It transforms ephemeral research into a permanent, machine-readable knowledge base that future agents can autonomously activate.
49
47
48
+
### `/onboard`
49
+
50
+
Your tool for rapid project orientation.
51
+
52
+
-**How it works:** Provides a high-signal overview of the repository's architecture, standards, and current state.
53
+
-**Why it works:** It ensures that you (and the agent) are always aligned with the project's unique conventions before starting a session.
54
+
50
55
---
51
56
52
57
## 💻 The Software Development Workflow
@@ -60,16 +65,11 @@ Your gateway to GitHub.
60
65
-**How it works:** Interfaces with the GitHub CLI to analyze open issues and recommend what to tackle next based on strategic impact.
61
66
62
67
63
-
### `/learn`
68
+
### `/scaffold`
64
69
65
-
Your tool for mastering new technologies and codifying them into project skills.
70
+
Your tool for project initialization.
66
71
67
-
-**How it works:** Implements a "Grounded Learning" philosophy through a 4-phase lifecycle:
68
-
1.**Environment Audit:** Automatically detects if the library is already installed or has local integration points.
69
-
2.**Strategic Mapping:** Researches the topic and defines 3-5 granular Learning Objectives (the "Learning Map"). **Requires user approval via `ask_user`.**
70
-
3.**Grounded Execution:** The specialized `learner` sub-agent performs real-world experiments (writing and running scripts) to verify "gotchas," performance, and idiomatic patterns.
71
-
4.**Skill Codification:** Consolidates all findings into a permanent project skill in `.gemini/skills/<name>/`, including a mandatory `SKILL.md` file and reference documents.
72
-
-**Why it works:** It transforms ephemeral research into a permanent, machine-readable knowledge base that future agents can autonomously activate.
72
+
-**How it works:** Scaffolds new components or entire projects using modern, standard tooling (TS, Python, Rust, etc.) and integrates the framework's standards and `makefile` from the start.
73
73
74
74
### `/task`
75
75
@@ -122,15 +122,15 @@ The approved plan is linked to a task. You trigger the execution:
122
122
123
123
After all steps pass, the agent presents the final work. Upon your approval, it merges back to `main` and cleans up the feature branch.
124
124
125
-
### Step 5: Document & Release with `/docs` & `/release`
126
-
127
-
Finally, use `/docs` to update the technical documentation and `/release` to publish the new version.
125
+
### Step 5: Document & Release with `/document` & `/release`
128
126
127
+
Finally, use `/document` to update the technical documentation and `/release` to publish the new version.
129
128
## 🔍 Walkthrough: Solving a Bug with `/debug`
130
129
131
-
When a bug is detected, the `/debug` command ensures a scientific resolution:
130
+
When a bug is detected, the `/debug` command ensures a scientific resolution using the specialized `debugger` subagent:
132
131
133
132
1.**Analyze Context:** The agent gathers all relevant logs and context.
133
+
...
134
134
2.**Formulate Hypothesis:** The agent proposes a root cause hypothesis (e.g., "The auth token is not being correctly passed to the header").
135
135
3.**Isolate & Test:** The agent creates a temporary branch `debug/hyp-auth-token`. It implements a minimal reproduction script or logging.
136
136
4.**RCA Synthesis:** Once confirmed, the agent generates a **Root Cause Analysis (RCA)** report. This report is used as the basis for the subsequent `/task work` to implement the fix on a feature branch.
0 commit comments