CLI Reference

Complete reference for the Conduct CLI commands.

conduct init

Initialize a conduct/ folder structure and configure AI agents.

Usage

conduct init

Interactive Prompts

1. AI Agent Selection: Choose which AI coding tools to configure

   • Cursor
   • Claude Code
   • Factory
   • OpenCode
   • GitHub Copilot
   • Warp

2. Issue Tracker Integration: Select issue trackers to integrate

   • GitHub Issues
   • Jira
   • Linear
   • GitLab Issues
   • Azure DevOps

3. Base Path Configuration: Set URLs for each selected tracker

   • Example: https://github.com/myorg/myrepo/issues/

What It Creates

Core Files

• conduct/spec.v0.md - Root specification file
• conduct/AGENTS.md - AI agent guidance document
• conduct/features/ - Feature specifications directory
• conduct/changes/ - Root-level changes directory
• conduct/track.json - Version and issue tracker configuration

Agent-Specific Files

Cursor

• .cursor/commands/feature.md
• .cursor/commands/change.md

Claude Code

• .claude/commands/conduct/feature.md
• .claude/commands/conduct/change.md
• CLAUDE.md (root-level instructions)

Warp

• .warp/commands/conduct/feature.md
• .warp/commands/conduct/change.md
• WARP.md (root-level instructions)

Factory

• .factory/commands/feature.md
• .factory/commands/change.md

OpenCode

• .opencode/command/feature.md
• .opencode/command/change.md

GitHub Copilot

• .github/prompts/conduct-feature.prompt.md
• .github/prompts/conduct-change.prompt.md

Example

$ conduct init
✔ Select AI agents to configure: Cursor, Claude, Warp
✔ Select issue trackers to integrate: GitHub
✔ Enter GitHub base path: https://github.com/myorg/myrepo/issues/
✅ Created conduct/ directory structure
✅ Configured 3 AI agents
✅ Integrated 1 issue tracker

conduct list

List all features and changes in the hierarchy.

Usage

conduct list

Output

Displays a tree view of:

• Feature hierarchy with version numbers
• Nested features and sub-features
• Changes under each feature
• Root-level changes

Example

$ conduct list
conduct/
├── spec.v0.md
├── features/
│   ├── authentication/
│   │   ├── spec.v2.md (current: v2)
│   │   ├── features/
│   │   │   └── oauth/
│   │   │       └── spec.v0.md
│   │   └── changes/
│   │       ├── add-2fa.spec.md
│   │       └── fix-session-timeout.spec.md
│   ├── dashboard/
│   │   ├── spec.v1.md (current: v1)
│   │   └── changes/
│   │       └── improve-performance.spec.md
│   └── api/
│       └── spec.v0.md
└── changes/
    ├── update-dependencies.spec.md
    └── improve-ci-cd.spec.md

conduct upgrade

Upgrade Conduct instructions to the latest version in all configured AI agents.

Usage

conduct upgrade

What It Updates

• conduct/AGENTS.md - Core agent instructions
• All agent command files (feature.md, change.md)
• Root-level instruction blocks in CLAUDE.md and WARP.md

When to Use

Run this command when:

• You upgrade the Conduct CLI to a new version
• New features are added to Conduct’s agent instructions
• You want to ensure all agents have the latest guidance

Example

$ conduct upgrade
✅ Updated conduct/AGENTS.md
✅ Updated .cursor/commands/feature.md
✅ Updated .cursor/commands/change.md
✅ Updated .claude/commands/conduct/feature.md
✅ Updated .claude/commands/conduct/change.md
✅ Updated CLAUDE.md
✅ Updated .warp/commands/conduct/feature.md
✅ Updated .warp/commands/conduct/change.md
✅ Updated WARP.md
✨ All agent instructions upgraded to latest version

AI Agent Commands

These commands are available within your configured AI agents (e.g., Cursor, Claude, Warp).

/feature

Create a new feature specification.

Usage in AI agent:

/feature <feature-name>

What it does:

1. Creates a new feature directory in conduct/features/
2. Generates spec.v0.md with proper structure
3. Creates nested features/ and changes/ subdirectories
4. Links to issue tracker (if configured)

Example:

/feature User authentication system

Creates: conduct/features/user-authentication-system/spec.v0.md

/change

Create a change specification for an existing feature.

Usage in AI agent:

/change <change-description>

What it does:

1. Prompts for parent feature (if multiple exist)
2. Creates change spec in feature’s changes/ directory
3. Automatically versions parent feature spec (v0 → v1, v1 → v2, etc.)
4. Updates track.json with new version
5. Links to issue tracker ticket (if configured)

Example:

/change Add two-factor authentication

Creates: conduct/features/user-authentication-system/changes/add-2fa.spec.md Updates: conduct/features/user-authentication-system/spec.v1.md

Configuration Files

track.json

Stores version and issue tracker configuration:

{
  "version": "1.0.0",
  "trackers": {
    "github": "https://github.com/myorg/myrepo/issues/",
    "jira": "https://mycompany.atlassian.net/browse/"
  },
  "features": {
    "authentication": {
      "version": 2,
      "path": "features/authentication"
    }
  }
}

AGENTS.md

Contains instructions for AI agents on how to:

• Create feature specifications
• Generate change specifications
• Follow naming conventions
• Structure nested hierarchies
• Link to issue trackers

This file is automatically generated and maintained by Conduct.

Tips & Best Practices

Feature Naming

• Use kebab-case: user-authentication, payment-gateway
• Be descriptive but concise
• Group related features in nested hierarchies

Change Descriptions

• Start with action verbs: “Add”, “Fix”, “Update”, “Remove”
• Be specific about what changed
• Reference issue tracker tickets

Version Management

• Conduct automatically manages versions
• Each change increments the parent feature version
• Old versions are preserved for audit trail
• Don’t manually edit version numbers

Nested Features

Create nested feature hierarchies for complex systems:

authentication/
├── spec.v0.md
└── features/
    ├── oauth/
    │   └── spec.v0.md
    ├── two-factor/
    │   └── spec.v0.md
    └── session-management/
        └── spec.v0.md

Use the /feature command within a feature’s context to create nested features.