grinrus/aidd-core
skills/aidd-core/SKILL.md
Aggregates shared runtime navigation and cross-skill ownership links. Use when resolving shared runtime entrypoints or ownership boundaries. Do not use when the request belongs to `aidd-policy` output/question rules or `status` summary reporting.
$ install --global
skillsauthnpx skillsauth add grinrus/ai_driven_dev aidd-coreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 8:05 PM18.8s49 files scanned
SKILL.md
- name:
- aidd-core
- description:
- Aggregates shared runtime navigation and cross-skill ownership links. Use when resolving shared runtime entrypoints or ownership boundaries. Do not use when the request belongs to `aidd-policy` output/question rules or `status` summary reporting.
- lang:
- en
- model:
- inherit
- user-invocable:
- false
Purpose
- This skill is the thin runtime-oriented navigation layer.
- Policy guidance (output contract, question format, read discipline, loop safety) lives in
feature-dev-aidd:aidd-policy. - Domain owners are split into dedicated shared skills (
aidd-docio,aidd-flow-state,aidd-observability,aidd-loop,aidd-rlm). - Agents may reference
feature-dev-aidd:aidd-coreas the topology entrypoint and navigation hub.
Canonical shared Python entrypoints
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-rlm/runtime/rlm_slice.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/diff_boundary_check.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/plan_review_gate.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/prd_review_gate.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/rlm_targets.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/skill_contract_validate.py
Command contracts
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/skill_contract_validate.py
- When to run: before release or CI checks when skill contract drift is suspected.
- Inputs: repository root plus optional filters for prompt/skill validation scope.
- Outputs: deterministic validation diagnostics for contract and prompt structure issues.
- Failure mode: non-zero exit when required contract fields/sections are missing or inconsistent.
- Next action: fix reported contract gaps in owners, then rerun the same validator.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-core/runtime/diff_boundary_check.py
- When to run: during loop/review orchestration before applying actions that may cross boundaries.
- Inputs: diff metadata (
--ticket,--scope-key, optional work-item context). - Outputs: boundary verdict (
ok|warn|blocked) and evidence references. - Failure mode: non-zero exit when diff inputs are missing or policy boundary checks fail.
- Next action: tighten scope/actions or hand off blocker, then rerun the boundary check.
Ownership guard
aidd-coreowns only aggregator-level shared runtime modules.- Policy/procedure text must be hosted in
feature-dev-aidd:aidd-policy.
Additional resources
- Policy contract: ../aidd-policy/SKILL.md (when: output/read/question rules are needed; why: apply shared policy without duplicating stage docs).
- DocIO runtime owner: ../aidd-docio/SKILL.md (when: actions/map/markdown tooling is needed; why: use canonical DocIO entrypoints from a dedicated shared skill).
- Flow/state runtime owner: ../aidd-flow-state/SKILL.md (when: stage state/progress/tasklist lifecycle tools are needed; why: use dedicated flow-state entrypoints).
- Observability runtime owner: ../aidd-observability/SKILL.md (when: diagnostics/inventory/log/report commands are needed; why: keep observability surface under a dedicated shared owner).
- Context pack template source: templates/context-pack.template.md (when: context pack format is unclear; why: confirm canonical sections generated by init/runtime).
Related Skills
grinrus/tasks-new
tools
VerifiedTrustedCommunity
Derives or refines tasklist items from PRD and plan artifacts. Use when tasklist stage prepares implementation-ready work items. Do not use when the request is plan authoring in `plan-new` or loop execution in `implement`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/status
testing
VerifiedTrustedCommunity
Generates consolidated ticket status summary and key artifact pointers. Use when checking current stage state or handoff readiness. Do not use when the request is diagnostics/inventory from `aidd-observability` or flow-state mutation via `aidd-flow-state`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/spec-interview
testing
VerifiedTrustedCommunity
Collects missing spec inputs and synchronizes answers into `spec.yaml`. Use when review-spec leaves unresolved specification fields. Do not use when the request is readiness gating in `review-spec` or task derivation in `tasks-new`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/review
testing
VerifiedTrustedCommunity
Runs review-stage validation for scope changes, findings, and follow-up task derivation. Use when review stage needs verdict and handoff tasks. Do not use when the request is direct implementation execution in `implement` or QA validation in `qa`.
5SKILL.mdUpdated Apr 5, 2026