All authors
Claude Skills by otaq-io
github.com/otaq-io15 skills0 installs32 views
- Readme ScreenshotsRefresh Otaq's README.md and its screenshots in docs/images/ from the real running app. Sets up a throwaway demo project (its own OTAQ_HOME, a small git repo, tickets, a ticket with a Plan of pieces, real Claude Code agents), stages a board with work in every column, captures the app window on macOS, then updates the README text and images to match. Use this whenever the user wants new or updated README screenshots, says the screenshots or README are out of date, wants images of the app for d...Votes: 0GitHub stars: 4
- Address ReviewAddress the review feedback on the Otaq ticket named by $OTAQ_TICKET after the user sent it back - get the context and the user's comment with `otaq prime`, read the line comments with `otaq review feedback`, fix them, commit everything, then end your stage again with a short comment through `otaq stage next`.Votes: 0GitHub stars: 4
- Answer QuestionAnswer a linked Otaq ticket's question from this finished ticket's conversation - get the context with `otaq prime`, answer only (change nothing), and reply with `otaq answer <ID> --stdin`.Votes: 0GitHub stars: 4
- CommitOtaq''s default Commit workflow skill - commit every change in this worktree (messages as the Agent instructions say, else "<KEY>: <what changed>"), before `otaq stage next`.Votes: 0GitHub stars: 4
- FlowChange an Otaq project's board flow as Noyan - read the current flow with `otaq flow show`, write the whole flow file (agents and stages, every field), give each stage a description of what it is for, ending with its source when you add or change it, propose it with `otaq flow propose --stdin`, then end your turn and wait for the user's Apply, Cancel or Ask for more changes as your next message.Votes: 0GitHub stars: 4
- Milestone PlanRun the Milestone plan stage of the Otaq ticket named by $OTAQ_TICKET - get the context with `otaq prime`, read what Product spec and Tech spec committed, decide the pieces and their order, write the ticket's Plan (the why, then the Pieces list) with `otaq update --plan-file`, write the plan into the project's docs where it keeps one and commit it, file no tickets, and end your stage with a comment through `otaq stage next`.Votes: 0GitHub stars: 4
- NoyanWork as Noyan, an Otaq project's coordinator - read `otaq prime --project`, name this conversation after the first request, take a light look at the code without editing or committing, write tickets whose notes hand on where the code lives, what you saw and the open questions, file several tickets only for separate deliverables, pass on only the stage choices the user names, and file them in Backlog with the otaq CLI.Votes: 0GitHub stars: 4
- Open PrOtaq's Open PR skill for a ticket's delivery as a pull request - push the confirmed branch and open the PR with `gh` or `az`, then report it with `otaq pr opened <url>`. In click mode the user already confirmed the branch, title and description in Otaq's dialog when you start; in automatic mode you first propose them with `otaq pr propose --stdin` and Otaq confirms at once, with no dialog.Votes: 0GitHub stars: 4
- Product SpecRun the Product spec stage of the Otaq ticket named by $OTAQ_TICKET - get the context with `otaq prime`, find what is undecided about what to build, for whom and why, ask the user one question at a time with `otaq ask human`, then write and commit the product decisions and docs where the project's notes say they live, and end your stage with a comment naming each file and decision through `otaq stage next`.Votes: 0GitHub stars: 4
- PushOtaq's default Push workflow skill - get the context with `otaq prime`, propose messages for the commits not yet on the PR's branch with `otaq pr propose --stdin`, and only once Otaq says they are confirmed (by the user, or at once in automatic mode) push them to the existing PR, then report it with `otaq pr opened <url>`.Votes: 0GitHub stars: 4
- RestackBring the Otaq ticket named by $OTAQ_TICKET up to date with the branch it merges into - get the context with `otaq prime`, rebase onto the target it names, resolve the conflicts, commit, then end your stage with a short comment through `otaq stage next`.Votes: 0GitHub stars: 4
- Tech SpecRun the Tech spec stage of the Otaq ticket named by $OTAQ_TICKET - get the context with `otaq prime`, read what Product spec committed on the branch, work out how to build it (asking the user with `otaq ask human` only where a choice changes what gets built), write and commit the architecture decisions and docs where the project's notes say they live, and end your stage with a comment naming each file and decision through `otaq stage next`.Votes: 0GitHub stars: 4
- ValidateValidate the Otaq ticket named by $OTAQ_TICKET as a read-only judge - get the context with `otaq prime --validate`, check the agent's change against the description, the checks and leftovers, then give a one- or two-line verdict with `otaq check pass|fail --stdin` that names the log of each check it ran.Votes: 0GitHub stars: 4
- Work TicketWork on the Otaq ticket named by $OTAQ_TICKET from start to review - get its context with `otaq prime`, follow the user's Agent instructions, check the ticket for gaps and ask what changes what gets built (options with pros and cons) before coding, decide by the size measure whether to build alone or write a Plan of pieces, implement (or, when the Plan has pieces, start a helper per piece, review, test and merge each, and re-split when the work grows or a helper hands back a piece too big), c...Votes: 0GitHub stars: 4
- Tasks**Depends on:** nothing. It quotes T1's refusal text, which is fixed in DECISIONS.md N11. **Runs in parallel with:** T1, T3, T4, T7. Read `ideas/noyan-intake/DECISIONS.md` first (N1–N4, N10, N11).Votes: 0GitHub stars: 4