adlc-core

Plugin adlc-core from marketplace vecton-adlc in Graphik-AI/adlc-skills. Commands read from the repo's manifest — 27 days ago.

Skills (21)

• acquire-codebase-knowledge

  Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narr

• code-review

  Review the actual requested diff against requirements and repository standards, including in-scope uncommitted work.

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• deslop

  Clean unnecessary material from the actual task diff while preserving behavior and safeguards.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• frontend-testing-debugging

  Verify rendered UI, interactions, responsive behavior and browser failures in the actual authorized app. Use for frontend testing or diagnosis; this does not initiate a redesign or scaffold a test framework.

• grill-with-docs

  Resolve consequential choices using focused grilling and useful domain documentation.

• grilling

  Stress-test consequential unresolved decisions through a focused human interview.

• implement-spec

  Coordinate implementation of a settled spec when its dependency graph benefits from it.

• implement

  Implement a bounded task, spec or ticket with relevant checks and review.

• post-implementation

  Close out authorized work with relevant documentation, evidence and scoped Git or tracker actions.

• pr

  Use when writing a PR body.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• research

  Investigate a bounded factual question against primary sources and record evidence.

• simplify

  Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

• systematic-debugging

  Investigate unexplained failures, regressions and unexpected behavior across the relevant code and runtime boundaries before making a supported fix.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• thermo-nuclear-code-quality-review

  Assess concrete structural maintainability concerns in a requested diff; distinguish defects from optional redesign.

• to-spec

  Synthesize agreed work into a proportionate implementation-ready specification.

• to-tickets

  Split agreed work into independently verifiable pieces when coordination helps.

• wayfinder

  Coordinate unresolved decisions across sessions using a map, dependencies and claims.

Similar plugins