project-setup

Automated GitHub repo onboarding parses a repository identifier from your message, validates ownership via the GitHub API, and registers the project in your workspace. It assigns a maintainer and installs six workflow templates to automate repository tracking.

Automated project tracking centralizes GitHub repository onboarding by turning each repo into a structured workspace project. It provisions six workflow missions and generates project.md and notes.md files to ensure repo activity is visible in briefs and triage scans.

Yes, GitHub API access is required to validate repository ownership during the project setup process. The automation checks your permissions for the repo owner/repo identifier before creating the tracked project and installing the workflow templates.

The best way to keep project notes updated is through the six installed workflow missions. These automated workflows continuously update notes.md with installation status and repository activity, feeding data into morning summaries and briefs.

Yes, you can track multiple GitHub repositories by providing the repo owner/repo identifier for each new project. The automation applies quick configuration, maintainer assignment, and workflow template installation across every validated repository.

Project setup requires workflow missions and project.md files to integrate repository tracking with workspace visibility. The six workflow templates automate repository processes, while project.md and notes.md ensure the project appears in briefs, triage scans, and summaries.