feat(workflow): integrate style-driven audits into draft and revise

Author: apiad

.gemini/commands/draft.toml

@@ -1,4 +1,4 @@
-description = "Interactive drafting workflow: gather context, create an outline, and generate a technical draft section-by-section."
+description = "Interactive drafting workflow: gather context, create an outline based on the Style Guide, and generate a technical draft section-by-section."
 
 prompt = """
 You are an expert technical writer. You are executing the custom `/draft` command workflow.
@@ -8,14 +8,15 @@ Follow these phases strictly:
 ### Phase 1: Context Gathering
 1.  **Analyze Request:** Identify the topic the user wants to draft.
 2.  **Search Context:** Search for existing context in `research/`, `plans/`, `TASKS.md`, and `journal/`. Use `list_directory` and `read_file`.
-3.  **Validate Context:** If no relevant research or planning context is found, use `ask_user` to suggest running `/research` or `/plan` first, or ask for more specific details.
+3.  **Read Style Guide:** Read the project's style guide at `.gemini/style-guide.md`.
+4.  **Validate Context:** If no relevant research or planning context is found, use `ask_user` to suggest running `/research` or `/plan` first, or ask for more specific details.
 
 ### Phase 2: Title and Path
 1.  **Propose Metadata:** Based on the gathered context, propose a title for the document and a target file path (e.g., `drafts/your-title.md`).
 2.  **Confirmation:** Use `ask_user` to get approval for the title and path.
 
-### Phase 3: Outline Creation
-1.  **Generate Outline:** Based on the context, generate a detailed Markdown outline (headers and brief descriptions of each section).
+### Phase 3: Outline Creation (Style Guide Driven)
+1.  **Generate Outline:** Based on the context and the rules in `.gemini/style-guide.md` (e.g., hooks, hierarchical headers, deep dives), generate a detailed Markdown outline.
 2.  **Review Loop:** Present the outline to the user and ask for feedback or approval. Use `ask_user` to refine the outline until the user is satisfied.
 
 ### Phase 4: Initialization
@@ -24,12 +25,12 @@ Follow these phases strictly:
 
 ### Phase 5: Section-by-Section Drafting
 1.  **Iterative Drafting:** For each section in the outline, invoke the `reporter` subagent.
-2.  **Instructions:** Instruct the `reporter` to fill the specific placeholder with detailed, high-quality prose based on the gathered context.
+2.  **Instructions:** Instruct the `reporter` to fill the specific placeholder with detailed, high-quality prose based on the gathered context. Ensure the `reporter` adheres to the general tone defined in the Style Guide.
 3.  **Review Progress:** After each section is filled, briefly update the user on the progress.
 
 ### Phase 6: Conclusion
 1.  **Final Summary:** Once all sections are filled, notify the user that the draft is complete.
-2.  **Next Steps:** Suggest using the `/revise` command to perform a structural and linguistic audit of the new draft.
+2.  **Next Steps:** Suggest using the `/revise` command to perform a structural and linguistic audit of the new draft based on the Style Guide.
 
 Do not skip any phases. Start with Phase 1.
 """

.gemini/commands/revise.toml

@@ -1,4 +1,4 @@
-description = "Interactive revision workflow: select a file, audit its structure and style, and iteratively improve it."
+description = "Interactive revision workflow: select a file, audit its structure and style based on the Style Guide, and iteratively improve it."
 
 prompt = """
 You are a Professional Editor. You are executing the custom `/revise` command workflow.
@@ -9,20 +9,23 @@ Follow these phases strictly:
 1.  **Select File:** Prompt the user to select a Markdown file for revision. Use `list_directory` (e.g., in `drafts/` or project root).
 2.  **Confirmation:** Confirm the file selection using `ask_user`.
 
-### Phase 2: Analysis and Audit
-1.  **Invoke Editor:** Invoke the `editor` subagent to analyze the selected file.
-2.  **Structural Audit:** Identify logical gaps, flow issues, or redundant sections.
-3.  **Linguistic Audit:** Identify grammar issues, awkward phrasing, and tone inconsistencies.
-4.  **Audit Report:** Present a concise summary of the findings to the user.
+### Phase 2: Analysis and Audit (Style Guide Driven)
+1.  **Read Style Guide:** Read the project's style guide at `.gemini/style-guide.md`.
+2.  **Invoke Editor:** Invoke the `editor` subagent to analyze the selected file based on the rules in the Style Guide.
+3.  **Step-by-Step Audit:** Instruct the `editor` to work through the document in phases as defined in the Style Guide:
+    -   **Phase 1 (Structural):** Narrative arc, headers, hooks, and deep dives.
+    -   **Phase 2 (Content & Substance):** Abstractions, concrete imagery, and subtext.
+    -   **Phase 3 (Linguistic):** Removing "AI-isms" like punchline em dashes and predictable triads.
+4.  **Audit Report:** Present a concise summary of the findings for the *current phase* to the user.
 
 ### Phase 3: Interactive Revision
-1.  **Proposed Changes:** For each identified improvement, propose a specific change.
+1.  **Proposed Changes:** For each identified improvement in the current phase, propose a specific change.
 2.  **Review Loop:** Use `ask_user` to present the proposed change and get approval before applying it.
 3.  **Apply Change:** Once approved, use `replace` (via the `editor` agent or directly) to apply the improvement to the target file.
-4.  **Repeat:** Continue this process for all major improvements until the user is satisfied.
+4.  **Next Phase:** Once a phase is complete and the user is satisfied, move to the next phase until all Style Guide phases are addressed.
 
 ### Phase 4: Finalization
-1.  **Summary:** Summarize all the changes made during the revision process.
+1.  **Summary:** Summarize all the changes made during the multi-phase revision process.
 2.  **Completion:** Confirm with the user that the revision is complete.
 
 Do not skip any phases. Start with Phase 1.