sparq:init

Initialize SparQ projects by creating sparq.config.json and scaffolding the .sparq directory.

27|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq:init
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-init
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The sparq:init skill automates the initial configuration setup for SparQ, enabling teams to bootstrap project-specific settings quickly and consistently.

Core Features & Use Cases

  • Auto-detect project tech stack from package.json and filesystem to configure SparQ
  • Create sparq.config.json and set up the .sparq directory structure for new projects or reinitialization
  • Guide users through interactive prompts to connect MCP sources, E2E setups, and export targets

Quick Start

Run /sparq:init to bootstrap SparQ configuration and generate the initial project scaffolding.

Frequently Asked Questions about sparq:init

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

FAQPage Schema
How do I bootstrap a new SparQ configuration for an existing project?

To bootstrap SparQ configuration, run the initialization command to auto-detect your tech stack, generate sparq.config.json, and scaffold the .sparq directory structure automatically.

Can I reinitialize SparQ setup without losing existing E2E configurations?

Yes, you can reinitialize SparQ setup safely. The process rebuilds the sparq.config.json and .sparq directory while applying interactive prompts to validate and preserve E2E configurations.

How does tech stack auto-detection work during SparQ project initialization?

Tech stack auto-detection reads your package.json and filesystem during project initialization, automatically assembling detected values to configure SparQ without manual entry.

What is the best way to set up E2E testing environments for new QA automation projects?

Setting up E2E testing environments is handled through interactive prompts during project initialization, guiding you to connect MCP sources and export targets for QA automation.

Do I need a package.json file to configure SparQ for QA automation?

While package.json enables tech stack auto-detection for QA automation, it is not strictly required. The initialization process prompts for missing inputs to satisfy the configuration schema.

What happens if required values are missing during SparQ initialization?

If required values are missing during SparQ initialization, the process pauses and issues interactive prompts to gather missing inputs, ensuring compatibility with the shared configuration schema.