Create repository documentation with product, tech, and feature specification templates.
npx skills add https://github.com/wizact/dotclaude --skill spec-setup
Please help me install this Agent Skill. Skill: spec-setup Source: https://github.com/wizact/dotclaude/tree/main/wizact-marketplace/plugins/speculator/skills/spec-setup Command: npx skills add https://github.com/wizact/dotclaude --skill spec-setup
This Skill automates the creation of a comprehensive, context-driven documentation structure for any repository, ensuring clear separation of concerns between product and technical details, and establishing a standardized pattern for feature specifications.
CLAUDE.md, docs/constitution/product.md, docs/constitution/tech.md, and feature templates.docs/features/README.md and templates for requirements.md, design.md, and tasks.md..claude/project_rules.md, CONVENTIONS.md) into tech.md./spec-setup to instantly establish a robust documentation foundation that adheres to best practices for clarity and maintainability.Use the spec-setup skill to establish a comprehensive documentation structure for the current repository.
High-intent search queries and answers about installing and using this skill.
You can automate project documentation setup by generating a multi-document constitution pattern with product.md and tech.md, alongside feature specification templates. This process analyzes your codebase to populate templates and establishes a clear separation of product and technical concerns.
A multi-document constitution pattern separates project context into distinct files like product.md and tech.md. This structure ensures clear separation of concerns between product details and technical conventions, making repositories easier to navigate and maintain.
Migrating existing convention files involves integrating content from files like .claude/project_rules.md and CONVENTIONS.md directly into the tech.md document. This consolidates scattered technical rules into the newly generated constitution structure.
Yes, you can generate language-agnostic feature specification templates. The setup creates a standardized feature directory containing requirements.md, design.md, and tasks.md templates that work across different programming environments.
The best way to structure feature specifications is to create a dedicated docs/features directory with standardized templates. This includes separate files for requirements, design, and tasks, ensuring consistent documentation for every feature.
No, existing convention files are not required. The setup analyzes your codebase to populate templates from scratch, but if convention files like CONVENTIONS.md exist, it migrates their content into the new tech.md document.
pradeepmouliExecute a script to generate baseline-spec.md and current-state.md from JSON output.
ormastesGenerate detailed design documents and agent task breakdowns from approved requirements and architecture.
EduardoJVNValidate code implementations against project specifications and design documents.
xloxn69Generates a complete user story template with YAML frontmatter and markdown sections.