Improve CLI init output - professional formatting with command focus

[dean0x]

Summary

The devflow init output should be more professional and user-focused. Users primarily care about what commands are available and how to use them.

Current State

The current output includes:

• Installation scope details
• Component installation status
• Manual merge warnings for settings/CLAUDE.md
• Full list of commands with brief descriptions
• Full list of skills with descriptions
• Technical notes about dual-mode patterns

This is overwhelming and mixes user-facing info with technical details.

Proposed Changes

Clean, Professional Output

✓ DevFlow v0.8.0 installed

Commands available:
  /catch-up         Get up to speed on project state
  /brainstorm       Explore design decisions
  /design           Create implementation plan
  /plan             Triage issues from discussion
  /breakdown        Break down tasks quickly
  /implement        Interactive implementation
  /code-review      Comprehensive code review
  /commit           Smart atomic commits
  /pull-request     Create PR with description
  /release          Automated releases
  /devlog           Document session progress
  /debug            Systematic debugging

Run any command in Claude Code to get started.

Docs: https://github.com/dean0x/devflow

Key Principles

1. Commands first - Users interact via commands, that's what they need to know
2. Clean formatting - No walls of text, no technical jargon
3. Actionable - Tell them what to do next
4. Hide internals - Skills, agents, settings merging are implementation details

Optional Verbose Mode

For users who want full details:

devflow init --verbose

This would show the current detailed output including:

• Installation paths
• Settings merge instructions
• Skills list
• Technical notes

Acceptance Criteria

• Default output is clean and command-focused
• Commands listed with brief, user-friendly descriptions
• No technical jargon in default output
• --verbose flag for detailed installation info
• Success/failure clearly indicated
• Link to documentation included

Technical Notes

• Modify src/cli/commands/init.ts
• Keep detailed logging available via verbose flag
• Ensure error states still show full context