skills.rest
scottopell
scottopellCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

propagate

Generate tests from Allium specifications for surface and spec-driven scopes.

1|Updated May 22, 2013
Search Tags:#test-generation#invariants#test-coverage#state-machine#propagation#allium#spec-testing
One-click install
npx skills add https://github.com/scottopell/dotfiles --skill propagate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propagate
Source: https://github.com/scottopell/dotfiles/tree/main/home-dir-configs/claude/skills/allium/skills/propagate
Command: npx skills add https://github.com/scottopell/dotfiles --skill propagate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate tests from Allium specifications to ensure test obligations align with spec intent, reducing manual effort and increasing confidence in test coverage.

Core Features & Use Cases

  • Surface mode: generates boundary and contract tests from surface declarations to verify APIs, UI contracts, and integration points.
  • Spec mode: walks the full test obligations derived from the Allium spec to produce comprehensive test suites including invariants, state transitions, and config tests.
  • Lifecycle guidance: supports deterministic propagation by mapping spec constructs to implementation bridges, outlining test requirements and recovery steps.
  • Prerequisites and workflow: requires an Allium spec file, a target codebase, and outputs from allium plan and allium model to guide test generation into the project's conventions.

Quick Start

Provide an Allium spec and a target codebase, then run the propagate tool to generate tests.

Frequently Asked Questions about propagate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate tests from Allium specifications?▼

To generate tests from Allium specifications, you provide the spec and a target codebase to map spec obligations to implementation, ensuring complete test coverage for invariants and state machines.

What is the difference between surface mode and spec mode for spec-driven test generation?▼

Surface mode generates boundary and contract tests from surface declarations to verify APIs, while spec mode walks full test obligations to produce comprehensive suites for invariants, state transitions, and config tests.

Do I need allium plan and allium model outputs to generate state machine tests?▼

Yes, you need the outputs of allium plan and allium model to map specification obligations to the implementation and drive the creation of state machine tests within your project conventions.

How do I ensure complete test coverage for specification invariants and contracts?▼

You ensure complete test coverage for invariants and contracts by walking the full test obligations derived from the Allium spec to produce comprehensive test suites mapping spec constructs to implementation bridges.

Can I verify API integration points using automatically generated boundary tests?▼

Yes, you can verify API integration points using automatically generated boundary and contract tests produced from surface declarations in your Allium specification.

Related Skills

Explore More Software Engineering Skills→
ravenoakravenoak

propagate

Generate deterministic tests from Allium specifications and plans.

Community
Advanced
cdalsoniiicdalsoniii

Domain Invariant Assertion

Analyze Go source and test files to verify domain invariants.

Community
Advanced
juxtjuxt
10

propagate

Generate unit, integration, property-based, and state machine tests from Allium behavioral specifications.

Official
Advanced
johan--johan--

convert-to-speckit

Convert manual reverse engineering documentation into GitHub Spec Kit specifications.

Community
Intermediate