What problem does it solve? New or forked repositories often lack clear development specs and contributing guides, leaving contributors and AI agents guessing about branch models, commit conventions, test gates, and review rules. This Skill generates both documentation sets in one guided pass, grounded in the repo's actual tooling and posture. ## Core Features & Use Cases - Development spec generation: Creates a root DEVELOPMENT.md covering branch/remote model, internal-change markers, upstream sync strategy, design records, versioning, and code-style guards, following the internal-fork pattern. - Contributing docs scaffolding: Writes four docs/contributing pages (index with routing, development setup, workflow and reviews, testing and documentation) modeled on the NeMo Relay structure. - Posture-aware conditionality: Detects whether the repo is upstream OSS, an internal fork, or internal-only from git remotes, and keeps or strips fork-specific sections accordingly. - Use Case: After forking an upstream project internally, run this once to produce a DEVELOPMENT.md with commit-prefix and anchor-comment rules plus a complete docs/contributing/ set, then wire pointers into AGENTS.md so future agents auto-load them. ## Quick Start Ask the agent to set up the development spec and contributing docs for this repository.
