Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

naxandros-pixel

@naxandros-pixel source repo

3 published skills

  1. ▌
    Delivery Planning · naxandros-pixel
    Builds a delivery timeline from an existing task board. Sequences work by dependency, derives a critical path, produces a Gantt or milestone view, and answers "when will this be done" with ranges, avoiding false precision. Use this skill whenever the user asks for a timeline, schedule, Gantt chart, milestone plan, release date, critical path, capacity or velocity estimate, or asks when something will be ready, including casual forms like "how long will this take" or "can we make it by the end of the month". Do not use this skill for what to work on next, what is blocked, or the order of upcoming work, since task-driven-development answers those from the board's queue. The discriminator is whether the answer needs a date, a duration, or a critical path. Pairs with task-driven-development, which produces the board this skill reads.
    0
    installs
  2. ▌
    Project Bootstrap · naxandros-pixel
    Sets up a new project for task-driven work. Creates a Kanban board with the standard Backlog / Ready / In progress / In review / Done columns, sets WIP limits, adds a priority field and issue template, records the board's identifiers in the project instruction file, and seeds the first tasks from whatever the owner described. Use this skill whenever a project is being started or a repository has no board yet, and whenever the user says something like "set up the board", "create a project", "how should I organise this work", "start a new repo", or "add WIP limits", or begins describing work on a project where no tracker exists. Pairs with task-driven-development, which runs the cycle this skill creates.
    0
    installs
  3. ▌
    Task Driven Development · naxandros-pixel bundle
    Use this skill whenever the user asks to build, implement, fix, refactor, or change anything in a project that has a board in GitHub Projects, Jira, or Notion, including casual phrasings like "add a login button", "fix this bug", or "let's start on the export feature" that never mention a task, ticket, epic, or board. Use it too when the user asks what to work on next, what is blocked, what state the work is in, or in what order upcoming work should happen, since those answers come from the board's queue. Runs a board-first development cycle where every change starts from a tracked task, large work is decomposed into atomic tasks under an epic or parent, board status moves automatically (In progress on start, In review when done), work happens on a per-task branch, and merging or deploying waits for the owner's explicit go-ahead. Hand a question to delivery-planning only when answering it needs a date, a duration, or a critical path.
    0
    installs