adlc-next

Plugin adlc-next from marketplace codex-is-all-you-need in BlueSkyXN/Codex-is-all-you-need. Commands read from the repo's manifest — today.

Skills (20)

• adlc-router

  ADLC Next guide. Recommends which ADLC Next skill, if any, fits a software request, with its exact command, and stops without doing the work. Use when the user invokes $adlc-next:adlc-router or /adlc-next:adlc-router, or asks which ADLC skill or workflow fits a request. Not for doing the work, and n

• adlc-setup

  Explicit-only ADLC Next setup. Use only when the user invokes $adlc-next:adlc-setup or /adlc-next:adlc-setup to create or update local/adlc/adlc-next.toml, the personal defaults that all worktrees of the repository share, for task files, delivery point, work items, design records, and language. Not

• ads-architecture

  Explicit-only ADLC architecture. Use only when the user invokes $adlc-next:ads-architecture or /adlc-next:ads-architecture to decide module structure, codebase layout, dependencies, interfaces, data ownership, or technical choices for a change, sized to its impact and recorded as a decision. Not for

• ads-domain

  Explicit-only ADLC domain modeling. Use only when the user invokes $adlc-next:ads-domain or /adlc-next:ads-domain to make business terms, rules, invariants, lifecycles, ownership, and boundaries explicit so code and specs agree with the business. Not for work that was not delegated through this comm

• ads-requirements

  Explicit-only ADLC requirements. Use only when the user invokes $adlc-next:ads-requirements or /adlc-next:ads-requirements to settle the problem, users, desired outcome, scope, constraints, and observable success conditions of a product or system change before design. Not for work that was not deleg

• ads-spec

  Explicit-only ADLC spec writer. Use only when the user invokes $adlc-next:ads-spec or /adlc-next:ads-spec to turn confirmed goals and design decisions into observable behaviors, edge and failure cases, and completion criteria with a verification method for each. Not for work that was not delegated t

• ads-survey

  Explicit-only ADLC project survey. Use only when the user invokes $adlc-next:ads-survey or /adlc-next:ads-survey to establish, with sources, how an existing project currently works on a question: structure, entry points, commands, existing decisions, constraints, and unknowns. Read-only. Not for wor

• improvement-prompt-eval

  Explicit-only ADLC prompt evaluation. Use only when the user invokes $adlc-next:improvement-prompt-eval or /adlc-next:improvement-prompt-eval to compare system prompts, instruction files such as AGENTS.md or CLAUDE.md, handoff prompts, or tool descriptions by their effect on representative tasks. No

• improvement-retro

  Explicit-only ADLC retrospective. Use only when the user invokes $adlc-next:improvement-retro or /adlc-next:improvement-retro to analyze a finished task, session, PR, or batch for recurring friction and propose, or when asked apply, the smallest changes to docs, rules, skills, tools, or checks that

• improvement-skill-eval

  Explicit-only ADLC skill evaluation. Use only when the user invokes $adlc-next:improvement-skill-eval or /adlc-next:improvement-skill-eval to test whether an agent skill triggers correctly and improves task outcomes, using representative cases written before running, a baseline, and judged results.

• sdlc-bugfix

  Explicit-only ADLC bug fixer. Use only when the user invokes $adlc-next:sdlc-bugfix or /adlc-next:sdlc-bugfix with a concrete defect or regression to reproduce, diagnose to its root cause, fix, and guard with a regression check. Not for work that was not delegated through this command.

• sdlc-clarify

  Explicit-only ADLC clarifier. Use only when the user invokes $adlc-next:sdlc-clarify or /adlc-next:sdlc-clarify to pin down the goal, scope, constraints, acceptance, or delivery point of a software request before work starts. Produces a clarified brief and does not implement. Not for work that was n

• sdlc-handoff

  Explicit-only ADLC handoff. Use only when the user invokes $adlc-next:sdlc-handoff or /adlc-next:sdlc-handoff to prepare an in-progress software task so another session, agent, or person can continue it without the original conversation. Not for work that was not delegated through this command.

• sdlc-implement

  Explicit-only ADLC implementer. Use only when the user invokes $adlc-next:sdlc-implement or /adlc-next:sdlc-implement with an already clear task description, spec, handoff, or task file, to implement it with self-checks and fixes. Not for framing an open problem, analysis-only requests, or work that

• sdlc-review

  Explicit-only ADLC reviewer. Use only when the user invokes $adlc-next:sdlc-review or /adlc-next:sdlc-review to check a change, branch, PR, or design against its current requirements and get findings classified as met, issue, or cannot judge. Not for work that was not delegated through this command.

• sdlc-ship

  Explicit-only ADLC delivery. Use only when the user invokes $adlc-next:sdlc-ship or /adlc-next:sdlc-ship to take an already verified change to a requested delivery point: commit, PR, merge, release or deployment, or verification in the real environment. Not for work that was not delegated through th

• sdlc-solve

  ADLC task owner. Carries a handed-over software task through investigation, design, implementation, verification, and rework to the requested delivery point, or resumes a paused ADLC task. Use when the user invokes $adlc-next:sdlc-solve or /adlc-next:sdlc-solve, names sdlc-solve or the ADLC workflow

• sdlc-test-first

  Explicit-only ADLC test-first driver. Use only when the user invokes $adlc-next:sdlc-test-first or /adlc-next:sdlc-test-first to build or change behavior through a red-green-refactor loop with automated tests. Not for work that was not delegated through this command.

• tasks-intake

  Explicit-only ADLC work intake. Use only when the user invokes $adlc-next:tasks-intake or /adlc-next:tasks-intake to turn ideas, defects, review findings, feedback, or task follow-ups into deduplicated work items with outcomes, done conditions, dependencies, and a proposed order. Not for work that w

• tasks-wrap-up

  Explicit-only ADLC batch wrap-up. Use only when the user invokes $adlc-next:tasks-wrap-up or /adlc-next:tasks-wrap-up to review a batch of work items or tasks against evidence: what finished, what is blocked, what was learned, what to adjust, and what the next batch should be. Not for work that was

Similar plugins