Create structured specifications from feature goals before implementation.
npx skills add https://github.com/supertyrelle/pelley --skill spec-supertyrelle
Please help me install this Agent Skill. Skill: spec Source: https://github.com/supertyrelle/pelley/tree/main/skills/spec Command: npx skills add https://github.com/supertyrelle/pelley --skill spec-supertyrelle
This Skill turns a vague feature goal into a complete, implementation-ready specification before any code is written, reducing ambiguity and rework.
Ask the spec skill to create a structured specification for your feature goal and include any known constraints or design preferences.
High-intent search queries and answers about installing and using this skill.
To create a structured specification from a feature goal, expand your short objective into a design document covering the problem statement, constraints, approach, contracts, rollout, and acceptance criteria using progressive elaboration before implementation begins.
Codebase-grounded analysis in software specification writing grounds your design document in the actual repository, ensuring the proposed architecture reflects existing patterns, boundaries, and reusable components rather than designing in isolation.
You need to write a technical specification for architectural changes when a cross-cutting decision requires alignment, validation, documented acceptance criteria, and review of existing patterns and public interfaces before development starts.
To validate a software design document for architectural risks, check the draft specification for factual issues, pattern conflicts, and architectural risks against the actual codebase before marking it ready for implementation.
Yes, you can use specification writing for evaluating multiple implementation options by applying progressive elaboration to document each approach, compare constraints, and establish validated acceptance criteria before committing to code.
Specification writing without an existing codebase skips the codebase-grounded analysis phase, meaning the design document will lack validation against existing patterns, boundaries, and reusable components, increasing the risk of integration conflicts.
AnthonyKazyakaAnalyze codebases to recommend relevant existing and custom skills.
beratcelik1Transform feature descriptions and bug reports into structured markdown implementation plans.
ThanhNguyenDatReview technical specification documents for ambiguities, gaps, and risks.
TruCol270Scan a focused codebase area and generate targeted documents in .planning/codebase/.
