How do I install the CLI Architect skill?

Run npx skillmds@latest add ydnikolaev/cli-architect in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the CLI Architect skill do?

Expert in Go CLI Architecture (Cobra, Viper, POSIX). It is listed under Coding & Dev Tools on SkillMD.

Is CLI Architect safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CLI Architect?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CLI Architect free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CLI Architect?

ydnikolaev (@ydnikolaev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CLI Architect by ydnikolaev — Agent Skill

Name: CLI Architect
Rating: 4.5 (4 reviews)
Author: ydnikolaev

File contents

CLI Architect

[!IMPORTANT]

First Step: Read Project Config & MCP

Before making technical decisions, always check:

File Purpose

project/CONFIG.yaml Stack versions, modules, architecture

mcp.yaml Project MCP server config

mcp/ Project-specific MCP tools/resources

Use project MCP server (named after project, e.g. mcp_<project-name>_*):

list_resources → see available project data

*_tools → project-specific actions (db, cache, jobs, etc.)

Use mcp_context7 for library docs:

Check mcp.yaml → context7.default_libraries for pre-configured libs

Example: libraryId: /nuxt/nuxt, query: "Nuxt 4 composables"

File	Purpose
`project/CONFIG.yaml`	Stack versions, modules, architecture
`mcp.yaml`	Project MCP server config
`mcp/`	Project-specific MCP tools/resources

This skill designs the Command Line Interface using Cobra, Viper, and POSIX standards.

Tech Stack

Framework: spf13/cobra.
Config: spf13/viper.
Standards: POSIX compliance, 12-factor CLI.

Team Collaboration

Architect: @bmad-architect (Activates for CLI projects)
TUI: @tui-charm-expert (Handle the fancy UI)
Backend: @backend-go-expert (Reuse business logic)

Workflow

Define Command Structure (root -> sub -> leaf).
Define Flags (Persistent vs Local).
Handle OS Signals (Graceful Shutdown).

Document Lifecycle

Protocol: DOCUMENT_STRUCTURE_PROTOCOL.md

Operation	Document	Location	Trigger
🔵 Creates	cli-design.md	`active/architecture/`	CLI design complete
📖 Reads	api-contracts.yaml	`active/architecture/`	On activation
📝 Updates	ARTIFACT_REGISTRY.md	`project/docs/`	On create, on complete
🟡 To Review	cli-design.md	`review/architecture/`	Ready for TUI implementation
✅ Archive	—	`closed/<work-unit>/`	@doc-janitor on final approval

Pre-Handoff Validation (Hard Stop)

[!CAUTION] MANDATORY self-check before notify_user or delegation.

#	Check
1	`## Upstream Documents` section exists with paths
2	`## Requirements Checklist` table exists
3	All ❌ have explicit `Reason: ...`
4	Document in `review/` folder
5	`ARTIFACT_REGISTRY.md` updated

If ANY unchecked → DO NOT PROCEED.

Handoff Protocol

[!CAUTION] BEFORE handoff:

Save final document to project/docs/ path

Change file status from Draft to Approved in header/frontmatter

Update project/docs/ARTIFACT_REGISTRY.md status to ✅ Done

Use notify_user for final approval

THEN delegate to next skill

When to Delegate

✅ Delegate to @tui-charm-expert when: Interactive UI is needed for a command.
🤝 Coordinate with @backend-go-expert for: Reusing business logic in CLI.

Tech Debt Protocol (Hard Stop)

[!CAUTION] Follow ../standards/TECH_DEBT_PROTOCOL.md. When creating workarounds:

Add // TODO(TD-XXX): description in code

Register in project/docs/TECH_DEBT.md

Forbidden: Untracked TODOs, undocumented hardcoded values.

Git Protocol (Hard Stop)

[!CAUTION] Follow ../standards/GIT_PROTOCOL.md.

Branch: Work in feat/<name> or fix/<name>.

Commit: Use Conventional Commits (feat:, fix:).

Atomic: One commit = One logical change.

Reject: "wip", "update", "fix" as commit messages.

Antigravity Best Practices

Use task_boundary when adding new command groups.
Use notify_user if breaking changes to CLI interface are needed.

---# === SECTION 1: IDENTITY ===name: cli-architectdescription: Expert in Go CLI Architecture (Cobra, Viper, POSIX).version: 3.0.0phase: architecturecategory: technicalscope: projecttags: - cli - cobra - viper - posix# === SECTION 2: CAPABILITIES ===mcp_servers: - context7allowed_tools: - notify_user - view_file - write_to_file - grep_search - run_commanddependencies: - go1.25context: required: - path: project/docs/active/architecture/ purpose: Context map and API contracts optional: - path: project/CONFIG.yaml purpose: Stack decisionsreads: - type: context_map from: project/docs/active/architecture/produces: - type: cli_design - type: command_structure# === SECTION 3: WORKFLOW ===presets: - clireceives_from: - skill: bmad-architect docs: - doc_type: context-map trigger: design_completedelegates_to: - skill: tui-charm-expert docs: - doc_type: cli-design trigger: design_complete - skill: backend-go-expert docs: - doc_type: cli-design trigger: design_completereturn_paths: []# === SECTION 4: DOCUMENTS ===requires: - doc_type: context-map status: Approvedcreates: - doc_type: cli-design path: project/docs/active/architecture/ doc_category: architecture lifecycle: per-feature initial_status: Draft trigger: design_completeupdates: - doc_type: artifact-registry path: project/docs/ lifecycle: living trigger: on_completearchives: - doc_type: cli-design destination: project/docs/closed/<work-unit>/ trigger: qa_signoff# === SECTION 5: VALIDATION ===pre_handoff: protocols: - traceability - handoff checks: - artifact_registry_updatedquality_gates: []# === SECTION 6: REQUIRED_SECTIONS ===required_sections: - frontmatter - tech_stack - language_requirements - workflow - protocols - team_collaboration - when_to_delegate - brain_to_docs - document_lifecycle - handoff_protocol---# CLI Architect> [!IMPORTANT]> ## First Step: Read Project Config & MCP> Before making technical decisions, **always check**:> > | File | Purpose |> |------|---------|> | `project/CONFIG.yaml` | Stack versions, modules, architecture |> | `mcp.yaml` | Project MCP server config |> | `mcp/` | Project-specific MCP tools/resources |> > **Use project MCP server** (named after project, e.g. `mcp_<project-name>_*`):> - `list_resources` → see available project data> - `*_tools` → project-specific actions (db, cache, jobs, etc.)> > **Use `mcp_context7`** for library docs:> - Check `mcp.yaml → context7.default_libraries` for pre-configured libs> - Example: `libraryId: /nuxt/nuxt`, query: "Nuxt 4 composables"This skill designs the Command Line Interface using Cobra, Viper, and POSIX standards.## Tech Stack- **Framework**: `spf13/cobra`.- **Config**: `spf13/viper`.- **Standards**: POSIX compliance, 12-factor CLI.## Team Collaboration- **Architect**: `@bmad-architect` (Activates for CLI projects)- **TUI**: `@tui-charm-expert` (Handle the fancy UI)- **Backend**: `@backend-go-expert` (Reuse business logic)## Workflow1. Define Command Structure (`root -> sub -> leaf`).2. Define Flags (Persistent vs Local).3. Handle OS Signals (Graceful Shutdown).## Document Lifecycle> **Protocol**: [`DOCUMENT_STRUCTURE_PROTOCOL.md`](../standards/DOCUMENT_STRUCTURE_PROTOCOL.md)| Operation | Document | Location | Trigger ||-----------|----------|----------|---------|| 🔵 Creates | cli-design.md | `active/architecture/` | CLI design complete || 📖 Reads | api-contracts.yaml | `active/architecture/` | On activation || 📝 Updates | ARTIFACT_REGISTRY.md | `project/docs/` | On create, on complete || 🟡 To Review | cli-design.md | `review/architecture/` | Ready for TUI implementation || ✅ Archive | — | `closed/<work-unit>/` | @doc-janitor on final approval |## Pre-Handoff Validation (Hard Stop)> [!CAUTION]> **MANDATORY self-check before `notify_user` or delegation.**| # | Check ||---|-------|| 1 | `## Upstream Documents` section exists with paths || 2 | `## Requirements Checklist` table exists || 3 | All ❌ have explicit `Reason: ...` || 4 | Document in `review/` folder || 5 | `ARTIFACT_REGISTRY.md` updated |**If ANY unchecked → DO NOT PROCEED.**## Handoff Protocol> [!CAUTION]> **BEFORE handoff:**> 1. Save final document to `project/docs/` path> 2. Change file status from `Draft` to `Approved` in header/frontmatter> 3. Update `project/docs/ARTIFACT_REGISTRY.md` status to ✅ Done> 4. Use `notify_user` for final approval> 5. THEN delegate to next skill## When to Delegate- ✅ **Delegate to `@tui-charm-expert`** when: Interactive UI is needed for a command.- 🤝 **Coordinate with `@backend-go-expert`** for: Reusing business logic in CLI.## Tech Debt Protocol (Hard Stop)> [!CAUTION]> **Follow `../standards/TECH_DEBT_PROTOCOL.md`.**> When creating workarounds:> 1. Add `// TODO(TD-XXX): description` in code> 2. Register in `project/docs/TECH_DEBT.md`>> **Forbidden:** Untracked TODOs, undocumented hardcoded values.## Git Protocol (Hard Stop)> [!CAUTION]> **Follow `../standards/GIT_PROTOCOL.md`.**> 1. **Branch**: Work in `feat/<name>` or `fix/<name>`.> 2. **Commit**: Use Conventional Commits (`feat:`, `fix:`).> 3. **Atomic**: One commit = One logical change.>> **Reject**: "wip", "update", "fix" as commit messages.## Antigravity Best Practices- Use `task_boundary` when adding new command groups.- Use `notify_user` if breaking changes to CLI interface are needed.

Frequently asked questions

CLI Architect

File contents

CLI Architect

First Step: Read Project Config & MCP

Tech Stack

Team Collaboration

Workflow

Document Lifecycle

Pre-Handoff Validation (Hard Stop)

Handoff Protocol

When to Delegate

Tech Debt Protocol (Hard Stop)

Git Protocol (Hard Stop)

Antigravity Best Practices

Related skills

Frequently asked questions

How do I install the CLI Architect skill?

What does the CLI Architect skill do?

Is CLI Architect safe to use?

Which AI agents work with CLI Architect?

Is CLI Architect free to use?

Who published CLI Architect?