docs: add CLI output convention and broaden audit scope

- Document cmd.Printf/cmd.Println convention in CONVENTIONS.md
- Add code pattern drift checking to audit-docs skill
- Add pre-flight checklist for CLI code in AGENT_PLAYBOOK.md
- Add task for AST-based linter test
- Fix package doc comment (initialize, not initcmd)

Signed-off-by: Jose Alekhinne <alekhinejose@gmail.com>

Author: josealekhine

.claude/commands/audit-docs.md

@@ -57,6 +57,21 @@ Review prose docs for internal consistency.
 - Outdated references to removed features
 - Tone inconsistencies
 
+### 4. Code Pattern Drift
+
+Check that code follows established conventions in CONVENTIONS.md.
+
+**Check for:**
+- CLI output methods: `fmt.Print*` instead of `cmd.Print*` in CLI code
+- Other patterns documented in CONVENTIONS.md
+
+**Method:**
+1. Read CONVENTIONS.md to understand established patterns
+2. Grep for violations (e.g., `fmt.Print` in `internal/cli/**/*.go`)
+3. Flag files that violate conventions
+
+**Files to scan:** `internal/cli/**/*.go` for CLI patterns
+
 ## Output Format
 
 Produce a structured report:
@@ -68,6 +83,7 @@ Produce a structured report:
 - X Go docstring issues found
 - Y CLI/docs mismatches found
 - Z narrative inconsistencies flagged
+- W code pattern violations found
 
 ## Go Docstring Issues
 
@@ -92,14 +108,22 @@ Produce a structured report:
 
 ### Outdated References
 - `docs/integrations.md:45` — References removed `--minimal` flag
+
+## Code Pattern Violations
+
+### CLI Output Methods
+- `internal/cli/task/run.go:127` — Uses `fmt.Printf` instead of `cmd.Printf`
+- `internal/cli/watch/run.go:45` — Uses `fmt.Println` instead of `cmd.Println`
 ```
 
 ## Execution
 
-1. **Scan Go files** for docstring patterns
-2. **Parse docs/*.md** for CLI references
-3. **Run ctx --help** variants to get actual CLI surface
-4. **Compare and report**
+1. **Read CONVENTIONS.md** to understand established patterns
+2. **Scan Go files** for docstring patterns
+3. **Parse docs/*.md** for CLI references
+4. **Run ctx --help** variants to get actual CLI surface
+5. **Check code patterns** against conventions (e.g., CLI output methods)
+6. **Compare and report**
 
 Do NOT auto-fix anything. This audit produces a report for human review.
 

.context/AGENT_PLAYBOOK.md

@@ -360,6 +360,24 @@ Never assume: If you don't see it in files, you don't know it.
 - If uncertain, say "I don't see this documented"
 - Trust files over intuition
 
+## Pre-Flight Checklist: CLI Code
+
+Before writing or modifying CLI code (`internal/cli/**/*.go`):
+
+1. **Read CONVENTIONS.md** — Load established patterns into context
+2. **Check similar commands** — How do existing commands in the same package handle output?
+3. **Use cmd methods for output** — `cmd.Printf`, `cmd.Println`, not `fmt.Printf`, `fmt.Println`
+4. **Follow docstring format** — See Go Documentation Standard below
+
+**Quick pattern check:**
+```bash
+# See how other commands do output
+grep -n "cmd.Printf\|cmd.Println" internal/cli/status/*.go
+
+# Spot violations in your changes
+grep -n "fmt.Printf\|fmt.Println" internal/cli/yourpackage/*.go
+```
+
 ## Go Documentation Standard
 
 When writing Go code, follow this docstring format consistently.

.context/CONVENTIONS.md

@@ -4,6 +4,31 @@
 
 ## Patterns
 
+### CLI Output Methods
+
+In CLI command code (`internal/cli/**/*.go`), always use Cobra's command methods
+for output instead of raw `fmt` functions:
+
+```go
+// ✓ Correct - uses cmd methods
+cmd.Printf("%s Done\n", green("✓"))
+cmd.Println("Status:")
+fmt.Fprintln(cmd.OutOrStdout(), "Output here")
+
+// ✗ Wrong - bypasses Cobra's output handling
+fmt.Printf("%s Done\n", green("✓"))
+fmt.Println("Status:")
+```
+
+**Why this matters:**
+- Cobra's `cmd.OutOrStdout()` respects output redirection in tests
+- Makes CLI commands testable without capturing os.Stdout
+- Consistent pattern across all commands
+
+**Exceptions:**
+- Helper functions that don't have access to `*cobra.Command` may use `fmt`
+- But prefer passing `io.Writer` or the command down to helpers
+
 ## Testing
 
 ## Documentation

.context/TASKS.md

@@ -48,6 +48,8 @@
 
 ## Backlog
 
+- [ ] Write AST-based test that warns if CLI functions use fmt.Print* instead of cmd.Print* #added:2026-01-29-171351
+
 - [ ] feat: ctx journal - LLM-powered session analysis and synthesis
 
 Parent command for working with exported sessions (.context/journal/):

internal/cli/initialize/doc.go

@@ -4,17 +4,14 @@
 //   \    Copyright 2026-present Context contributors.
 //                 SPDX-License-Identifier: Apache-2.0
 
-// Package initcmd implements the "ctx init" command for initializing a
+// Package initialize implements the "ctx init" command for initializing a
 // .context/ directory with template files.
 //
 // The init command creates the foundation for persistent AI context by
 // generating template files for constitution rules, tasks, decisions,
 // learnings, conventions, and architecture documentation. It also sets
 // up Claude Code integration with hooks and slash commands.
 //
-// Note: This package is named "initcmd" because "init" is a reserved
-// keyword in Go for package initialization functions.
-//
 // # File Organization
 //
 //   - init.go: Command definition and flag registration

internal/templates/AGENT_PLAYBOOK.md

@@ -284,6 +284,24 @@ the codebase. Periodic consolidation prevents this from compounding.
 
 When in doubt, ask: "Would a new contributor understand where this belongs?"
 
+## Pre-Flight Checklist: CLI Code
+
+Before writing or modifying CLI code (`internal/cli/**/*.go`):
+
+1. **Read CONVENTIONS.md** — Load established patterns into context
+2. **Check similar commands** — How do existing commands in the same package handle output?
+3. **Use cmd methods for output** — `cmd.Printf`, `cmd.Println`, not `fmt.Printf`, `fmt.Println`
+4. **Follow docstring format** — See Go Documentation Standard below
+
+**Quick pattern check:**
+```bash
+# See how other commands do output
+grep -n "cmd.Printf\|cmd.Println" internal/cli/status/*.go
+
+# Spot violations in your changes
+grep -n "fmt.Printf\|fmt.Println" internal/cli/yourpackage/*.go
+```
+
 ## Go Documentation Standard
 
 When writing Go code, follow this docstring format consistently.