aircury/ai-framework110 installs

spec-kit-analyse

Q: How do I install this agent skill?

Run npx skills add https://github.com/aircury/ai-framework --skill spec-kit-analyse.

Q: Is this agent skill safe to install?

Review the displayed partner audits, complete source, permissions, dependencies, and exact revision before installing.

Read-only cross-artifact consistency check across spec.md, plan.md, and tasks.md. Detects gaps, conflicts, and FRAMEWORK.md violations before implementation begins.

How do I install this agent skill?

npx skills add https://github.com/aircury/ai-framework --skill spec-kit-analyse

view source ↗

Is this agent skill safe to install?

Gen Agent Trust Hubpass
The skill 'Spec-Kit Analysis' by Aircury is designed to perform read-only consistency checks on project artifacts such as specifications, plans, and task lists. It ensures alignment between user stories and tasks while verifying compliance with governing principles. The primary security consideration is the indirect prompt injection surface, as the skill processes external markdown files that could contain malicious instructions. However, the skill is scoped to read-only operations and includes explicit guardrails.
Socketpass
No alerts
Snykpass
Risk: LOW · No issues

What does this agent skill do?

Perform a read-only consistency analysis after the task list has been generated.

Input: Optionally specify a change name. If omitted, infer from context or ask.

This skill makes no file modifications.

Steps

Load artifacts

Load the change artifacts under specs/changes/<name>/:
- spec.md (required)
- plan.md (required)
- tasks.md (required)
If tasks.md is missing, prompt to use the spec-kit-tasks skill first.

Also load FRAMEWORK.md as the governing principles baseline.

Run consistency checks

Analyze across these dimensions:

Dimension	What to check
Coverage	Every user story in spec.md has corresponding tasks in tasks.md
Alignment	Plan architecture matches spec goals and constraints
FRAMEWORK.md compliance	No dependency rule violations, no anemic domain model, ports present for external dependencies
Duplication	Overlapping requirements or tasks
Ambiguity	Vague terms without measurable criteria
Terminology drift	Same concept named differently across artifacts
Orphans	Tasks with no corresponding requirement, or requirements with no tasks

Produce findings

Output a structured findings table:

## Analysis: <change-name>

### Findings
| ID | Severity | Dimension | Description | Location |
|----|----------|-----------|-------------|----------|

### Coverage Summary
| Requirement | Task IDs |
|-------------|----------|

### FRAMEWORK.md Violations
<List any violations. CRITICAL severity — must be fixed before proceeding.>

### Metrics
- Total findings: N
- Critical: N | High: N | Medium: N | Low: N

### Recommended Next Actions
<Ordered list of what to fix.>

Severity: CRITICAL (FRAMEWORK.md violation) > HIGH > MEDIUM > LOW.

Output

After the analysis:

If CRITICAL findings exist: "Fix FRAMEWORK.md violations before proceeding. Do not use the spec-kit-implement skill until these are resolved."
If no critical findings: "Use the spec-kit-implement skill to execute the validated task list."

Guardrails

Read-only. Never modify any file.
FRAMEWORK.md violations are always CRITICAL — never downgrade or ignore them.
Deterministic: re-running on the same artifacts produces the same findings.

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/aircury/ai-framework/spec-kit-analyse">View spec-kit-analyse on skillZs</a>