spec-writer

Generate or rewrite structured Markdown specifications for the BrandPortal .NET repository.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/quockidang/share-agent-SKILL --skill spec-writer-quockidang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/quockidang/share-agent-SKILL/tree/main/skills/spec-writer
Command: npx skills add https://github.com/quockidang/share-agent-SKILL --skill spec-writer-quockidang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill tackles the challenge of manually crafting detailed technical specifications for .NET projects, which often leads to inconsistencies and time loss, by automating the generation and refinement of structured specs.

Core Features & Use Cases

  • Spec Generation: Creates feature, technical, or service specs from business requirements, existing code, or documents.
  • Rewriting and Tagging: Rewrites specs from AppServices or BA docs, applying tags like [new], [update], or [delete] for changes.
  • Use Case: For a photo category management feature, input the description and get a ready-to-implement Markdown spec outlining API, DB impacts, and tasks.

Quick Start

Invoke the spec-writer skill to create a technical spec for the photo category management feature in the BrandPortal repo.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I generate a technical spec for a .NET repository from a business document?

To generate a technical spec from a business document, provide the business requirements to the spec-writer. It produces a ready-to-implement Markdown specification detailing API impacts, database changes, and tasks for the .NET repository.

What is the best way to rewrite an existing service spec with change tags?

Rewriting an existing service spec is done by providing the AppServices or BA docs to the spec-writer. It generates a rewritten Markdown specification that applies [new], [update], or [delete] tags to clearly mark implementation changes.

Can I create a feature spec in Vietnamese for the BrandPortal .NET repository?

Yes, you can create structured Markdown feature specs in Vietnamese. The spec-writer adheres to the BrandPortal repo architecture and templates to output specifications that satisfy Vietnamese verification requirements.

Does the spec-writer work without external dependencies for markdown generation?

Yes, the spec-writer operates without external dependencies to generate Markdown. It uses internal references and assets to map business requirements into structured technical specifications for your .NET project.

When do I need to use change tags like [new] or [update] in a technical spec?

Change tags like [new], [update], or [delete] are used when rewriting existing service specifications. They are applied during the spec generation process to explicitly identify modifications planned for the .NET implementation.

What limitations exist when generating feature specs from existing code?

When generating feature specs from existing code, outputs are constrained to the BrandPortal .NET repository architecture. The resulting Markdown specifications specifically detail API and database impacts rather than general architectural redesigns.