adlc commands

43 tagged adlc, measured the same way as everything else here.

Browse within: adlc-toolkit 28ai-coding-assistant 15compression 15

ReviewDev

01

Evyasys-Software-Solutions/EvyaGovernance

Command

Independent code review — AC coverage, correctness, security, YAGNI, test quality. Evidence-based findings (file+line). Critical issues block FinishDev.

7 20d ago A 32 tokens original MIT

TrainDocs

02

Evyasys-Software-Solutions/EvyaGovernance

Command

Scan the entire project and generate 37 quality-gate documents into .evyasys/docs/ — covering architecture, standards, patterns, testing, security, deployment, design system, UI/UX standards, accessibility (WCAG 2.1 AA), visual quality contracts, styling tokens, hook rules, dependency governance, complete unit testing…

7 20d ago A 97 tokens original MIT

Update

03

Evyasys-Software-Solutions/EvyaGovernance

Command

Update the Evyasys plugin and manage context compression — shows version diff, changelog highlights, asks for confirmation, then always asks about compression state. Project config, credentials, docs, and board artefacts are never touched.

7 20d ago A 45 tokens original MIT

architect

04

shamimfahad/adlc-toolkit

Command Cursor

Design the architecture and task breakdown for a REQ. Phase 2 of /proceed. Dispatches codebase-explorer to inform the design, then drafts architecture.md and tasks/TASK-.md. On high-stakes REQs, dispatches the architecture-adversary to attack the design before the gate so the user reviews a stress-tested plan. Ends in…

5 19d ago A 85 tokens

autopilot

05

shamimfahad/adlc-toolkit

Command Cursor

Autonomous end-to-end pipeline. Runs /spec → /architect → /implement → /review → /wrapup like /proceed, but instead of pausing at each gate it routes the decision through the decision-maker agent, commits its work as it goes, and ends in a single final human review backed by a full audit log. Opt-in; conservative by…

5 19d ago A 84 tokens

bugfix

06

shamimfahad/adlc-toolkit

Command Cursor

Streamlined pipeline for bug fixes. Slimmer than /proceed — bug report → investigate → fix → verify → ship, with gates between each. Use for defects, not for new features. Larger or scope-creeping bugs should be re-framed as a REQ via /spec.

5 19d ago A 58 tokens