Back to list
allen-hsu

tech-spec-writer

by allen-hsu

0🍴 0📅 Jan 18, 2026

SKILL.md


name: tech-spec-writer description: Create comprehensive technical specification documents through interactive Q&A. Use when (1) user asks to write a Tech Spec, (2) user wants to plan a new feature, (3) user needs to create technical documentation for a feature, (4) user mentions "tech spec", "technical specification", or "feature planning document".

Tech Spec Writer

Create structured technical specification documents through an interactive workflow that gathers context before generating the complete document.

Workflow

Phase 1: Context Gathering

Ask questions in stages to avoid overwhelming. Start with core questions, then dive deeper based on answers.

Stage 1 - Core Context:

  1. What is the feature/project name?
  2. What problem does this solve? (1-2 sentences)
  3. What is the main goal? (measurable outcome)

Stage 2 - Solution Details: 4. What is your proposed solution? (high-level approach) 5. What systems/components will be affected? 6. Are there any architectural changes? (new services, APIs, database changes)

Stage 3 - Technical Specifics: 7. Schema changes needed? (new tables, fields) 8. API changes? (new/modified endpoints) 9. UI changes? (if applicable)

Stage 4 - Risks & Planning: 10. Known risks or technical challenges? 11. Implementation phases or milestones? 12. Key metrics to measure success?

Adapt questions based on previous answers. Skip irrelevant sections.

Phase 2: Document Generation

After gathering context, generate the complete Tech Spec using the template in references/template.md.

For section-specific writing guidelines, see references/section-guide.md.

Phase 3: Output Formatting

Provide two output formats:

Option A: Markdown (default)

  • Clean markdown suitable for GitHub, Notion, or general use

Option B: Confluence

  • Use Confluence wiki markup format
  • See references/confluence-format.md for conversion rules
  • Ready to paste into Confluence editor (switch to wiki markup mode)

Ask user which format they prefer, or provide both.

Quick Reference: Template Sections

SectionRequiredDescription
MetadataYesStart Date, Owner, Version, Change Log
Problem StatementYesWhat problem this solves
GoalYesMeasurable objectives
Proposed SolutionYesHigh-level approach
ChangesYesSummary of all changes
Architectural DiagramsIf applicableSystem architecture changes
Schema SpecificationIf applicableDatabase changes
API SpecificationIf applicableEndpoint changes
UI Flow DiagramsIf applicableUser interface changes
RiskYesPotential challenges and mitigations
Security & PrivacyOptionalSecurity considerations
Alternative SolutionsRecommendedOther approaches considered
Implementation PlanYesPhases and timeline
MetricsYesSuccess measurement
Software Quality AttributesOptionalNon-functional requirements
Follow UpYesAction items

Resources

Score

Total Score

45/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

0/5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon