Initialize Specwright by detecting the development stack and generating configuration files.
npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-init
Please help me install this Agent Skill. Skill: sw-init Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/sw-init Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-init
This Skill automates the initial setup of Specwright within a project, ensuring all necessary configurations, anchor documents, and quality gates are established based on the project's stack and user preferences.
.specwright/config.json), foundational documents (CONSTITUTION.md, CHARTER.md), and initializes state files.Run the sw-init skill to set up Specwright in the current project directory.
High-intent search queries and answers about installing and using this skill.
To initialize Specwright project configuration, run the sw-init skill in your project directory. It scans the codebase to detect languages and frameworks, then interactively gathers your development practices to generate config files and foundational documents.
Automated project stack detection scans your codebase to identify package managers, test runners, and frameworks. This ensures the generated development standards and quality gates match your specific technical environment and Git workflow preferences.
Yes, you can use Specwright init to generate a project constitution and charter. The process involves conversing with you for qualitative inputs regarding project vision, which establishes foundational documents alongside quality gates and hooks.
The best way to set up quality gates and hooks is through guided configuration initialization. The skill detects your development stack and asks about your quality expectations to configure these gates automatically within the generated configuration files.
Specwright initialization works with both existing codebases and new projects. It scans the current directory to identify existing technical details and combines them with your user inputs to establish development standards and project vision.
Qualitative inputs are needed during project initialization to capture your development practices, quality expectations, and Git workflow preferences. While codebase scanning handles technical details, your inputs establish the project vision and constitution.
hector-mannyRun JavaScript files with the bun runtime and toolchain.
swingermanValidates DAE artifacts for schema correctness and cross-artifact consistency with read-only error reports.
KrismithReddy12Calculate a weighted 0-10 code quality score from linters and test runners.
deMGoncalvesValidate phase transitions against quality gates and project standards.