scope-cli

Manage local-first issues as markdown snapshots and JSONL events via CLI.

27|2|Updated Jul 11, 2014
One-click install
npx skills add https://github.com/jimmyhmiller/PlayGround --skill scope-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-cli
Source: https://github.com/jimmyhmiller/PlayGround/tree/main/codex-experiments/agile-tools/skills/scope-cli
Command: npx skills add https://github.com/jimmyhmiller/PlayGround --skill scope-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Scope CLI provides a command-line workflow to manage local-first issues stored as markdown snapshots with corresponding JSONL event logs, making issue tracking fast, repeatable, and audit-friendly within a repository.

Core Features & Use Cases

  • Create, list, show, update, and delete issues from the command line in a local-first workflow.
  • Manage comments, project mappings, and index status to keep issues consistent across snapshots and events.
  • Use references to read the full specification and schema for reliable integration with existing docs.

Quick Start

Initialize a project with the scope CLI and then manage issues by creating, listing, and showing them.

Frequently Asked Questions about scope-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage local-first issues stored as markdown snapshots from the command line?

You can manage local-first issues stored as markdown snapshots by using the scope CLI to create, list, show, update, and delete issues directly within your repository. It pairs markdown snapshots with JSONL event logs for fast, repeatable issue tracking.

What is the scope CLI used for in project management?

The scope CLI is used for project management to track local-first issues, comments, indexes, and project mappings. It provides an audit-friendly, command-line workflow that stores issues as markdown snapshots with corresponding JSONL event logs.

Can I track issue comments and project mappings in a local repository without a remote database?

Yes, you can track issue comments and project mappings locally without a remote database. The scope CLI manages these elements entirely within your repository using markdown snapshots and JSONL event logs for local-first consistency.

How do I initialize a project to start tracking issues with markdown and JSONL events?

To start tracking issues, initialize your project using the scope CLI's initialization command. This sets up the local-first environment so you can immediately begin creating, listing, and viewing issues stored as markdown and JSONL.

Does the scope CLI support conflict resolution for local-first issue tracking?

Yes, the scope CLI supports conflict resolution as part of its local-first issue tracking workflow. This ensures that markdown snapshots and JSONL event logs remain consistent and audit-friendly across command-line operations.

What are the limitations of using markdown snapshots and JSONL events for issue management?

Using markdown snapshots and JSONL events for issue management relies on frontmatter-based discovery and command-line workflows. It is designed for development teams and individual repositories, meaning it may not suit teams requiring centralized web interfaces.