How to structure your repository for seamless integration with the Constellation project management system.
I'm Owen — a lifelong wheelchair user with muscular dystrophy. A few things that shape how I work:
Typing is difficult for me. I rely heavily on AI coding assistants (Cursor, Windsurf, Claude) to write code and documentation. When interacting with me:
- Offer choices as A, B, C options — I can type a single letter instead of explaining my preference
- Be proactive — Make decisions and implement rather than asking for confirmation on every detail
- Propose complete solutions — Don't ask me to type out requirements; infer from context and iterate
Accessibility is personal. Many of my projects (Nimbus, Octavium, MacroVox, Adaptive Clothing) are accessibility-focused because I'm building tools I actually need.
PowerShell is my preferred shell. I work on Windows and use PowerShell for command-line tasks. I prefer single-line commands when possible for efficiency.
This guide goes into new repos first. If you're an AI assistant and this document is in the repo, use it to understand context before diving in.
Constellation is a meta-repository that aggregates status, TODOs, and context from multiple independent projects. It enables:
- Cross-project visibility and coordination
- AI-assisted project management (Cursor, Windsurf, etc.)
- Automated status dashboards
Your repo remains fully autonomous — Constellation just reads from it.
To integrate with Constellation, your repo should have:
- README.md — Project overview, purpose, current state
- TODO.md (or equivalent) — Pending tasks in checkbox format
- Consistent structure — See recommendations below
Your README is the primary source of context. Include:
# Project Name
Brief description of what this project does.
## Status
Current state: **Active** | **In Development** | **Stable** | **Planning**
## Features
- Feature 1
- Feature 2
## Quick Start
How to run/use the project.- Screenshots — Visual context for AI tools and humans
- Tech Stack — Languages, frameworks, dependencies
- Project Structure — Directory overview
Constellation scans for pending tasks using checkbox syntax. Use one of these files:
| File Name | Common Use |
|---|---|
TODO.md |
General task list |
NEXT_STEPS.md |
Sequential phases/steps |
ROADMAP.md |
Feature roadmap |
Use GitHub-flavored markdown checkboxes:
## Current Sprint
- [ ] Uncompleted task
- [x] Completed task
- [ ] Another pending item
## Backlog
- [ ] Future feature
- [ ] Nice to have- Group by category or phase — Easier to scan
- Keep items actionable — "Add user auth" not "Think about auth"
- Mark completed items —
[x]helps track progress - Bold key items —
- [ ] **High priority task**
A quick-reference file for AI assistants working on your repo:
# LLM Notes
Quick reference for AI assistants.
## Project Context
What this project is and why it exists.
## Key Files
| File | Purpose |
|------|---------|
| `src/main.py` | Entry point |
| `config.json` | Settings |
## Conventions
- Naming conventions
- Code style preferences
- Things to avoid
## Owner Context
Any personal context relevant to the project (e.g., accessibility requirements, target users).For quick status visibility, add a status section:
## Current Status
| Area | Status |
|------|--------|
| Core Features | ✅ Complete |
| UI | 🔄 In Progress |
| Documentation | ⏳ Planned |
| Tests | ❌ Not Started |
**Next Milestone:** v1.0 release
**Blockers:** NoneConsistent structure across repos makes cross-project work easier:
your-project/
├── README.md # Required: Project overview
├── TODO.md # Required: Task tracking
├── LICENSE # Recommended: MIT or similar
├── requirements.txt # Python: dependencies
├── package.json # Node: dependencies
├── src/ # Source code
├── docs/ # Extended documentation
├── tests/ # Test files
└── assets/ # Images, icons, etc.
Constellation's sync_status.py script reads:
- TODO.md (or NEXT_STEPS.md, ROADMAP.md) — Extracts unchecked items
- README.md — Used for project context
| From Your Repo | Into Constellation |
|---|---|
| Unchecked TODOs | PROJECT_STATUS.md next steps |
| Completed/total counts | Progress percentages |
| README context | Project descriptions |
Constellation's dashboard.py checks:
- Branch name
- Uncommitted changes
- Ahead/behind remote
When providing commands or examples, use PowerShell syntax. Owen prefers single-line commands for efficiency:
Running Python scripts:
python scripts/sync_status.pyNavigating and running commands:
cd C:\Users\Owen\dev\my-project; python src/main.pyChecking file contents:
Get-Content README.mdRunning with arguments:
python scripts/dashboard.py --fetchListing files:
Get-ChildItem -Path src -Filter *.py- Use semicolons (
;) to chain commands on one line - Prefer
Get-Contentovercatfor file reading - Use
Get-ChildItemorlsfor directory listing - PowerShell is case-insensitive for cmdlets but case-sensitive for file paths on some systems
my-project/
├── README.md
├── TODO.md
└── src/
└── main.py
README.md:
# My Project
A tool that does something useful.
## Status
**In Development** — Core features working, UI in progress.
## Quick Start
python src/main.pyTODO.md:
# TODO
## Current
- [ ] Finish UI layout
- [ ] Add settings dialog
- [x] Core functionality
## Backlog
- [ ] Add tests
- [ ] Write documentationReach out to Owen or refer to the Constellation README for workflow details.