dev-cycle

Plugin dev-cycle from marketplace dev-cycle-skills in pavelbender/dev-cycle-skills. Commands read from the repo's manifest — today.

Skills (13)

• automation

  Set up and manage the scheduled unattended jobs of the dev-cycle plugin for the current repository, all in one pass or one by one: check the project profile, plan the intervals and start times so that the collectors feed the workers, dry-run each job, install collect-issues, collect-backlog, autodeb

• coding-rules

  Rules for how coding agents write, split, organise, edit and verify code: file budgets by tokens and lines, single responsibility, contracts first, side-effect isolation, minimal diffs, verification before claiming done (cs-001…cs-028). Use when writing, refactoring or reviewing code, or when execut

• consilium

  Convene a consilium: 4–5 role agents (architects, developer, QA, UI/UX, release manager, researcher) study one hard question independently, each from its own domain, then challenge each other's positions; the chair records a consensus or a reasoned decision with the dissent. The most expensive decis

• cycle

  Route a feature through the development cycle: detect the bundle's current stage from its files and frontmatter, run the next stage (plan-scenarios → plan-feature → write-task passes draft/detail/slices/validation → run-bundle → tidy-folder) and stop only at gates that need the user. The single entr

• execute-task

  Implement a development task from its task file: compare the task with current code, implement, test, update docs, set the status and the _DONE/_VAL suffix. Use when asked to implement, execute or carry out a task file ("implement task", "execute T05", «реализуй задачу из», «выполни задание», «сдела

• fix

  Fix a bug from a report: a sentence, a screenshot, an error text, a log or a failing test. Reproduce the defect, find the root cause, then take the shortest path the cause allows: a direct fix with a regression test, a briefed developer with an independent check, or a planned change through cycle. T

• plan-feature

  Plan a new feature or a change of existing behaviour as repository documentation: an umbrella workflow (01-workflow.md) with target model and invariants, an impact map, and a dependency-ordered task sequence (02-task-sequence.md) with TNN tasks and PNN proof points. Use when asked to plan, decompose

• plan-scenarios

  Plan interactive user scenarios for a GUI or terminal UI before technical planning: actors, scenario map, interaction flows, screen and command state contract, controls and permissions, acceptance criteria. Produces 00-interaction-scenarios.md in a feature bundle. Use when a request is about screens

• run-bundle

  Coordinate the execution of a feature bundle: pick ready tasks from 02-task-sequence.md and frontmatter, run each through execute-task and validate-task in its own git worktree (in parallel when tasks touch disjoint code, otherwise in sequence), merge validated work into the bundle branch, and the b

• task-layout

  Contract for development-cycle documents: feature bundle layout (scenarios, workflow, task sequence, task files, evidence), TNN/PNN/SNN identifiers, task-file frontmatter and status suffixes, readiness, language of artifacts, and the project profile the other dev-cycle skills read. Use when creating

• tidy-folder

  Tidy one documentation folder: classify files as canonical, active task, historical, index or noise; move closed cycles to _completed/; add or refresh the routing index; fix every inbound link. Use when asked to clean up, declutter or reorganise a docs folder («приберись в папке», «убери шум из docs

• validate-task

  Validate a completed development task against its task file: check every acceptance criterion with proof from code, tests and commands, classify each drift as benign or bug, check failure paths, fix or escalate, set status validated and the _VAL suffix. Use when asked to validate, verify, accept or

• write-task

  Write or refine a development task file in a feature bundle, in one of four passes: draft (bounded stub), detail (sections verified against code), slices (subagent-ready SNN items), validation (acceptance criteria and test commands polished). Builds the status map from the task sequence and frontmat

Subagents (2)

• consilium-member

  Read-only member of a dev-cycle consilium: studies one question from the lens its brief assigns and returns a position with evidence. It cannot edit files or run commands. Use only when the consilium skill seats a member.

• researcher

  Read-only researcher for the dev-cycle skills: finds facts in code and documents and returns them with file:line evidence. It cannot edit files or run commands. Use only when a dev-cycle skill delegates a lookup, an evidence pack or a drift check.

Similar plugins