starintel-repo-bootstraplisted

# StarIntel repository bootstrap ## Goal Create one explicitly approved repository and seed its issue tracker with a small, traceable set of issues from the project's ADARD source. This skill does not implement the application or deploy it. ## Inputs and output Input must include the target owner/name, purpose, visibility, authoritative ADARD source repository, and issue or design scope. Output is a minimal repository plus idempotently created issues that preserve source links, approval state, dependencies, and acceptance criteria. ## Rules - Load `adadr` for research/design approval semantics and `skill-portability` before retaining any source material. - Use `gh` for every GitHub operation. - Inspect authoritative repositories before creating a target. A missing name is not evidence that a new repository is needed. - Never create duplicates, forks, transfers, licenses, application code, or language-specific files during bootstrap. - Never close or edit ADARD source issues. - Never treat an open issue, green CI, or repository creation as approval. - Never infer that a new aggregate repository owns work mapped to an existing implementation repository. ## Workflow 1. Read applicable repository instructions and inspect local Git status. Keep unrelated changes untouched. 2. Run `gh auth status`, list organization and account-visible repositories, and inspect same-purpose candidates with `gh repo view`. 3. Confirm the ADARD source repository and inspect the