levelup-implement

Automating pull request creation from accepted CDRs involves compiling the decisions into context modules and draft skills, then orchestrating Git branch setup and PR publishing to a team repository. This workflow generates a tracking artifact and a comprehensive PR description ready for review.

A CDR tracking artifact is a generated markdown file placed in the context_modules directory to record accepted Context Decision Records. It consolidates decisions and related artifacts into a comprehensive PR description for team review before merging into the team-ai-directives repository.

Yes, generating draft PRs from context modules requires a clean working tree. The workflow performs environment checks and operates across Git branch creation, skill publishing, and PR creation, requiring a configured team repository and credentials for push operations.

Yes, you can automatically generate and update context modules including rules, personas, examples, and constitution based on accepted CDRs. The workflow integrates these decisions, copies draft skills into the target repository, and updates the skills manifest.

The best way to consolidate context modules and skills into a team repository is orchestrating environment checks, branch setup, and integration of accepted CDRs. This approach copies draft skills, updates the skills manifest, and produces a tracking artifact with a comprehensive PR description.