All authors
Claude Skills by AI-native-Systems-Research
github.com/AI-native-Systems-Research90 skills0 installs138 views
- Speckit TasksGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.Votes: 0GitHub stars: 2
- Speckit TaskstoissuesConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.Votes: 0GitHub stars: 2
- Tools Spin ModelCreate a new Spin/Promela formal verification model for a system propertyVotes: 0GitHub stars: 2
- Speckit AnalyzePerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.Votes: 0GitHub stars: 2
- Speckit ChecklistGenerate a custom checklist for the current feature based on user requirements.Votes: 0GitHub stars: 2
- Speckit ClarifyIdentify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.Votes: 0GitHub stars: 2
- Speckit ConstitutionCreate or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.Votes: 0GitHub stars: 2
- Speckit ImplementExecute the implementation plan by processing and executing all tasks defined in tasks.mdVotes: 0GitHub stars: 2
- Speckit PlanExecute the implementation planning workflow using the plan template to generate design artifacts.Votes: 0GitHub stars: 2
- Speckit SpecifyCreate or update the feature specification from a natural language feature description.Votes: 0GitHub stars: 2
- Speckit TasksGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.Votes: 0GitHub stars: 2
- Speckit TaskstoissuesConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.Votes: 0GitHub stars: 2
- Component Sync SpecsEnsure a component implementation is synchronized with its specifications.Votes: 0GitHub stars: 2
- Component Update DocsEnsure the per-component README.md are up to date and correctly reflect the code.Votes: 0GitHub stars: 2
- Speckit DriftAnalyze drift between specs and implementation. Compares requirementsVotes: 0GitHub stars: 2
- Speckit Sync AnalyzeAnalyze drift between specs and implementation. Compares requirementsVotes: 0GitHub stars: 2
- Speckit Sync ApplyApply approved drift resolutions to specs and/or codeVotes: 0GitHub stars: 2
- Speckit Sync BackfillGenerate a new spec from unspecced code feature (backfill)Votes: 0GitHub stars: 2
- Speckit Sync ConflictsDetect and surface conflicts between specs or between specs and designVotes: 0GitHub stars: 2
- Speckit Sync ProposePropose resolutions for detected drift. AI generates spec updates orVotes: 0GitHub stars: 2
- Speckit PlanExecute the implementation planning workflow using the plan template to generate design artifacts.Votes: 0GitHub stars: 2
- Speckit SpecifyCreate or update the feature specification from a natural language feature description.Votes: 0GitHub stars: 2
- Speckit AnalyzePerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.Votes: 0GitHub stars: 2
- Speckit ChecklistGenerate a custom checklist for the current feature based on user requirements.Votes: 0GitHub stars: 2
- Speckit ClarifyIdentify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.Votes: 0GitHub stars: 2
- Speckit ConstitutionCreate or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.Votes: 0GitHub stars: 2
- Speckit ConvergeAssess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.Votes: 0GitHub stars: 2
- Speckit ImplementExecute the implementation plan by processing and executing all tasks defined in tasks.mdVotes: 0GitHub stars: 2
- Speckit PlanExecute the implementation planning workflow using the plan template to generate design artifacts.Votes: 0GitHub stars: 2
- Speckit SpecifyCreate or update the feature specification from a natural language feature description.Votes: 0GitHub stars: 2
- Speckit TasksGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.Votes: 0GitHub stars: 2
- Speckit TaskstoissuesConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.Votes: 0GitHub stars: 2
- Speckit SpecifyCreate or update the feature specification from a natural language feature description.Votes: 0GitHub stars: 2
- Build Property InventoryBuild the ONE tool-independent, source-traced verifiable-property inventory for a component and bundle every property onto the I<component> public methods that implement it. Reconciles two independent, BLIND per-artifact extractions (spec and code, isolated from each other) into a single ID-keyed set with owning-method bundles and counts. Does NOT name a prover and does NOT record proof status — that is added downstream. This is Role 1 (the single source of truth) that `tools-verify-*-with-pr...Votes: 0GitHub stars: 2
- Tools Aggregate Coverage By InterfaceRender the ONE combined per-component scoring page (`<component>_scoring.html`) from the reconciled `unified_properties.yaml` — per-tool KPI cards, a combined Creusot|Kani scorecard over the public-method bundles, property-bundle and spec-vs-each-tool tables, unproved-causes, measurement, anti-vacuity, and provenance. Consumes the Role-1 property set + Role-2 per-tool status blocks that already live in `unified_properties.yaml`; attaches nothing new. Does NOT extract, bundle, or prove — the i...Votes: 0GitHub stars: 2
- Speckit Git FeatureCreate a feature branch with sequential or timestamp numberingVotes: 0GitHub stars: 2
- Speckit Git ValidateValidate current branch follows feature branch naming conventionsVotes: 0GitHub stars: 2
- Component SweepFast breadth-first TRIAGE across many Certus components — property inventory and spec-vs-code divergence list only, no proving. Produces the three property YAMLs per component (the same files `component-verify` Step 2 consumes) plus a cross-component divergence report, in hours rather than the days a full prover pass costs. Use it to decide WHERE to spend prover time, and to get the property denominators for every component. It never proves, never scores, never touches a branch. It is NOT a s...Votes: 0GitHub stars: 2
- Component VerifyOne-command, repeatable formal-verification pipeline for a single Certus component — new or already-verified. Pulls a fresh tree off origin/unstable, extracts the tool-independent property inventory (Role 1), proves it with Creusot AND Kani (Role 2), renders one combined scoring HTML (Role 3), then commits to two per-component verif branches (overwrite-in-place, component-folder-only gate) — each branch carrying the FULL metadata bundle (spec_properties + code_properties + unified_properties ...Votes: 0GitHub stars: 2
- Refute Tool BoundaryAdversarially attack a single formal-verification tool-boundary claim. Given a component, a tool (creusot|kani), and a property id the scorer scored `tool-boundary`, this skill runs as an INDEPENDENT agent (different from the one that produced the artifact) whose only job is to BREAK the wall — apply the full lever arsenal plus anything the battery has not yet encoded, and either land a reproducible proof (refuted) or exhaust every avenue (upheld). Separation of powers: the prover argues the ...Votes: 0GitHub stars: 2