Metadata-Version: 2.4
Name: planhub
Version: 0.0.1
Summary: Sync local planning files to GitHub Issues.
Project-URL: Homepage, https://github.com/your-org/planhub
Project-URL: Repository, https://github.com/your-org/planhub
Author: Planhub Maintainers
License: MIT
Keywords: github,issues,milestones,planning,sync
Classifier: Development Status :: 2 - Pre-Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Requires-Python: >=3.10
Requires-Dist: build>=1.4.0
Requires-Dist: twine>=6.2.0
Description-Content-Type: text/markdown

# Planning Sync Service

This repository hosts the main CLI app, `planhub`, that syncs local planning
artifacts (plans, issues, milestones written as `.md` files) to GitHub Issues
via API.

## Goals
- Keep planning artifacts in git and reviewable.
- Generate/update GitHub issues and milestones from local files.
- Make planning conversational: we can edit `.md` files and sync later.

## Proposed Architecture
We split the system into two parts:
1. **CLI app (this repo)**: handles GitHub API communication and syncing.
2. **Data repo**: contains the `plans/`, `issues/`, and `milestones/` files.

The CLI will scaffold the data repo and then sync it on demand.

## Commands
- `planhub init`
  - Creates the standard folder structure in the current git repo:
    `plans/`, `issues/`, `milestones/`, and `docs/`.
- `planhub sync`
  - Reads the `.md` files and creates/updates GitHub issues/milestones.

## Suggested Data Repo Layout
```
plans/
issues/
milestones/
docs/
```

## Next Steps
- Finalize the file formats (see `docs/`).
- Implement `init` and `sync` commands.
- Add CI to validate the file format.
