-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Description
Bullet points (special arrows and emojis) of "Execution Flow" and "Quick Guidelines" are not properly "copied" from spec.md, and are turning into unrecognized chars.
Examples:
spec template | spec |
---|---|
→ | � |
✅ | � |
and so on (see excerpt below).
Maybe you guys could just skip those and use regular bullets or dashes in the template :)
Using Claude Sonnet 4.
# Feature Specification: Allow Tagging Segments
**Feature Branch**: `001-allow-tagging-segments`
**Created**: 2025-09-14
**Status**: Draft
**Input**: User description: "Allow tagging segments so that users can filter them by tags"
## Execution Flow (main)
1. Parse user description from Input
� If empty: ERROR "No feature description provided"
2. Extract key concepts from description
� Identify: actors, actions, data, constraints
3. For each unclear aspect:
� Mark with [NEEDS CLARIFICATION: specific question]
4. Fill User Scenarios & Testing section
� If no clear user flow: ERROR "Cannot determine user scenarios"
5. Generate Functional Requirements
� Each requirement must be testable
� Mark ambiguous requirements
6. Identify Key Entities (if data involved)
7. Run Review Checklist
� If any [NEEDS CLARIFICATION]: WARN "Spec has uncertainties"
� If implementation details found: ERROR "Remove tech details"
8. Return: SUCCESS (spec ready for planning)
---
## � Quick Guidelines
- � Focus on WHAT users need and WHY
- L Avoid HOW to implement (no tech stack, APIs, code structure)
- =e Written for business stakeholders, not developers