What problem does it solve? Setting up a milestone-based agentic workflow requires every project to declare its forge, repository, branching rules, agent map, verification commands, and issue labels — without a shared configuration, every other workflow skill would have to ask the same questions on every run. ## Core Features & Use Cases - Automatic detection: Runs a forge-detection script to identify the git forge (GitHub or Gitea), host, owner/repo, and default branch, then confirms findings with the user instead of guessing. - Guided configuration interview: Derives area mappings from existing project agents, extracts verification commands from real project files (package.json, Makefile, pyproject.toml, etc.), and asks only about what cannot be detected. - Safe writes and label creation: Creates or updates only the Workflow (sagittaras) section of CONTRIBUTING.md without touching the rest of the file, migrates older config locations, and creates missing issue labels in the tracker only after confirmation. - Use Case: A developer clones a repository and wants to start planning milestones with the sagittaras plugin. Running this skill once produces a complete workflow configuration that plan-milestone, run-milestone, and verify-issue all read from. ## Quick Start Ask the assistant to set up the milestone workflow configuration for this project.
