Compare commits

..

2 Commits

Author SHA1 Message Date
Den Delimarsky 🌺
919ba00198 Update specify.md 2025-09-18 23:21:26 -07:00
Den Delimarsky 🌺
4e869cb11a Update __init__.py 2025-09-18 23:13:38 -07:00
2 changed files with 7 additions and 10 deletions

View File

@@ -77,7 +77,7 @@ BANNER = """
╚══════╝╚═╝ ╚══════╝ ╚═════╝╚═╝╚═╝ ╚═╝
"""
TAGLINE = "Spec-Driven Development Toolkit"
TAGLINE = "GitHub Spec Kit - Spec-Driven Development Toolkit"
class StepTracker:
"""Track and render hierarchical steps without emojis, similar to Claude Code tree output.
Supports live auto-refresh via an attached refresh callback.
@@ -951,15 +951,11 @@ def init(
step_num = 2
steps_lines.append(f"{step_num}. Start using slash commands with your AI agent:")
steps_lines.append(" [bold cyan]/constitution[/] - Establish project principles")
step_num += 1
steps_lines.append(f"{step_num}. [bold cyan]/specify[/] - Create specifications")
step_num += 1
steps_lines.append(f"{step_num}. [bold cyan]/plan[/] - Create implementation plans")
step_num += 1
steps_lines.append(f"{step_num}. [bold cyan]/tasks[/] - Generate actionable tasks")
step_num += 1
steps_lines.append(f"{step_num}. [bold cyan]/implement[/] - Execute implementation")
steps_lines.append(" 2.1 [bold cyan]/constitution[/] - Establish project principles")
steps_lines.append(" 2.2 [bold cyan]/specify[/] - Create specifications")
steps_lines.append(" 2.3 [bold cyan]/plan[/] - Create implementation plans")
steps_lines.append(" 2.4 [bold cyan]/tasks[/] - Generate actionable tasks")
steps_lines.append(" 2.5 [bold cyan]/implement[/] - Execute implementation")
steps_panel = Panel("\n".join(steps_lines), title="Next steps", border_style="cyan", padding=(1,2))
console.print()

View File

@@ -8,6 +8,7 @@ scripts:
Given the feature description provided as an argument, do this:
1. Run the script `{SCRIPT}` from repo root and parse its JSON output for BRANCH_NAME and SPEC_FILE. All file paths must be absolute.
**IMPORTANT** You must only ever run this script once. The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for.
2. Load `templates/spec-template.md` to understand required sections.
3. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.
4. Report completion with branch name, spec file path, and readiness for the next phase.