spec

Validate development plans against a codebase and generate implementation guides.

2|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/slinkardbrandon/slynk-toolkit --skill spec-slinkardbrandon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/slinkardbrandon/slynk-toolkit/tree/main/skills/spec
Command: npx skills add https://github.com/slinkardbrandon/slynk-toolkit --skill spec-slinkardbrandon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you validate and refine your plans against the codebase before committing to non-trivial work, saving time and reducing errors.

Core Features & Use Cases

  • Codebase Exploration: Analyze files, patterns, tests, and recent changes.
  • Plan Validation: Identify gaps, contradictions, and potential issues.
  • Structured Plan Generation: Create a detailed implementation guide.
  • Use Case: When planning a feature or refactoring, use this Skill to explore the codebase, ask targeted questions, and generate a structured plan.

Quick Start

Run the 'spec' skill with the issue number or description to start a new session.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I validate a development plan against an existing codebase?▼

Plan validation analyzes your codebase files, patterns, and recent changes to identify gaps, contradictions, and potential issues before building. It generates a structured implementation guide to ensure codebase readiness and reduce errors during non-trivial software development.

What is the best way to stress-test a software feature plan before implementation?▼

Stress-testing a feature plan involves exploring the codebase to ask targeted questions and validate assumptions. It identifies potential issues and missing context, ultimately producing a detailed, structured implementation guide to refine your approach before committing to development.

Do I need to provide context files for codebase analysis and plan validation?▼

Yes, you need to provide context files and codebase access for accurate plan validation. The analysis requires examining actual files, patterns, tests, and recent changes to correctly identify gaps and generate a reliable implementation guide.

When should I use codebase exploration for specification and plan validation?▼

Use codebase exploration for specification and plan validation when planning a feature or refactoring. It helps you identify gaps, contradictions, and potential issues before committing to non-trivial work, saving time and reducing errors during the software development lifecycle.

Can I generate an implementation guide directly from an issue description?▼

Yes, you can generate an implementation guide by running a validation session with an issue number or description. The tool explores the codebase, asks targeted questions to refine the plan, and outputs a structured guide for the development work.