sdlaic

Plugin sdlaic from marketplace bienwithcode in bienwithcode/SDLAIC. Commands read from the repo's manifest — 13 days ago.

Skills (11)

• apply

  Use when tasks.md exists and is approved. Executes the task list one task at a time — each task is verified before moving to the next. No scope expansion allowed.

• brainstorm

  DEPRECATED — do not use. The monolithic design phase has been split into three phase-gated 1:1 skills. Use `proposal` (scope), then `spec` (behavior), then `design` (architecture), each behind its own grill/review gate.

• design

  Use to author design.md for a change — the Technical Architecture phase (Phase 2). Runs after an approved spec and an optional design grill, producing the architecture that satisfies the proposal and spec, then hands off to the review gate.

• enforcer

  Use when the agent starts a new turn or receives any request. This is the global methodology router — it MUST run before any other skill to determine the correct phase and enforce workflow discipline.

• grillme

  Parameterized Socratic challenge engine. Runs BEFORE drafting an artifact (proposal | spec | design | tasks), loading the matching references/grills/<phase>-grill.md and challenging one question at a time. Hands agreed resolutions back for the draft skill to apply into the artifact's content section

• new

  Use when starting new work, a user provides a Jira key, or the enforcer routes to the initialization phase. Creates an SDLAIC change with full context from Jira and codebase research.

• plan

  Use after the design phase is approved (proposal → spec → design complete). Translates the approved design into granular, ordered tasks — one [TEST:<level>] task per guarantee, each embedding its own RED → IMPL → GREEN cycle with the test definition frozen at plan time. Each task must be completable

• proposal

  Use to author proposal.md for a change — the Scope Proposal (Phase 1A). Runs after an optional scope grill and produces a single artifact defining business rationale and an explicit IN-SCOPE vs OUT-OF-SCOPE contract, then hands off to the review gate.

• review

  Parameterized auditor & gatekeeper engine. Runs AFTER an artifact is drafted (proposal | spec | design | tasks | code), loading the matching references/reviews/<phase>-audit.md in a clean subagent and issuing an APPROVE / REQUEST_CHANGES / REJECT verdict. Verdicts are persisted via `sdlaic gate set`

• spec

  Use to author specs/<capability>/spec.md for a change — the Behavioral Requirements phase (Phase 1B). Runs after an approved proposal and an optional spec grill, producing requirements stated as testable guarantees with compact example tables, then hands off to the review gate.

• write-pr-description

  Use to author the GitHub PR description for review. Checks whether the SDLAIC change directory is inside the PR's git repo (and, if inside, committed) so artifacts the reviewer can't see are never referenced, then emits a tight, review-focused description — ticket/issue link (Jira or GitHub issue, w

Subagents (2)

• code-quality-reviewer

  Assesses whether changed code is architecturally sound and would survive a CURe PR review. Runs code research queries (workspace's chosen tool), evaluates 11 CURe critical checks (DRY, module boundaries, security, performance, etc.), checks scope, and reports reusability patterns.

• compliance-reviewer

  Audits committed code against SDLAIC contracts (proposal, specs, design — in that authoring order) for compliance. Compares implementation against what was specified, checks for missing/extra/drift, verifies scope and requirements coverage.