Setup Custom Skills

Scaffold the per-repository configuration that the workflow skills assume. Four decisions:

• Issue tracker: the system of record for published issues, either local markdown under backlog/ or a remote tracker (GitHub, GitLab, Jira, or one you describe)
• Ticket writing convention: the built-in to-tickets format, or an existing project template or ticket-writing skill
• Triage roles: the strings this repository uses for the two category and four state roles
• Domain documentation: where CONTEXT.md and architecture decision records live, and the consumer rules for reading them

Refinement is not a decision. Whatever tracker a repository picks, it drafts in .refinement/ and publishes only when the user asks. A remote tracker with its own refinement or analysis status changes nothing here: local drafting comes first, publication pushes the result. refinement.md holds those conventions and every generated tracker file carries them.

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.

Process

1. Explore

Look at the current repository to understand its starting state. Read whatever exists; don't assume: