33 tagged adlc, measured the same way as everything else here.
Browse within: adlc-toolkit 18ai-coding-assistant 15compression 15
Evyasys-Software-Solutions/EvyaGovernance
Skill Claude CodeCodex
Batch-decomposes one or more user stories (or all stories in an epic) into developer-ready subtasks (max 5 per story: 4 implementation + 1 QA). Builds shared technical context once — no per-story re-scanning. Each task includes AC Coverage Map, Data Flow, Error & Recovery, and Technical Guidance — no code. Detects…
Evyasys-Software-Solutions/EvyaGovernance
Skill Claude CodeCodex
Use this skill to run a comprehensive read-only health check of the Evyasys plugin install and project state. Covers 20 checks across 6 areas — plugin install (dir resolution, all commands/skills/workflows present, compression engine status), project config (project.yaml validity, credentials decrypt, PM tool and…
Evyasys-Software-Solutions/EvyaGovernance
Skill Claude CodeCodex
One-time (or update) configuration wizard — confirms project folder, checks existing config, validates PM tool credentials live, collects notification credentials, and persists non-sensitive config to .evyasys/project.yaml with encrypted credentials to /.evyasys/credentials.
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
Multi-perspective code review for a REQ. Phase 4 of /proceed. Dispatches 4 read-only review agents in parallel (correctness, quality, architecture, reflector) — plus a 5th ui-reviewer that runs the app in a browser when the change touches a UI surface — consolidates findings by severity, and ends in the verify gate.
Skill Claude CodeCodex
Slim ADLC pipeline for small changes — a tweak, a small feature, a contained refactor that's too small for /proceed's five phases but should still live in the vault. Triage → plan (gate) → implement → review + ship (gate). Self-triaging: recommends /proceed if the work is actually large, up front or mid-flight…