codexspec 0.5.0__tar.gz → 0.5.2__tar.gz

{codexspec-0.5.0 → codexspec-0.5.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.5.0
+Version: 0.5.2
 Summary: CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code
 Project-URL: Homepage, https://github.com/Zts0hg/codexspec
 Project-URL: Repository, https://github.com/Zts0hg/codexspec

{codexspec-0.5.0 → codexspec-0.5.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codexspec"
-version = "0.5.0"
+version = "0.5.2"
 description = "CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code"
 readme = "README.md"
 requires-python = ">=3.11"

{codexspec-0.5.0 → codexspec-0.5.2}/src/codexspec/translator.py

@@ -282,8 +282,8 @@ def extract_frontmatter_fields(content: str) -> dict[str, Optional[str]]:
         result["description"] = desc_match.group(1).strip()
 
     # Extract argument-hint (can be multiline with |)
-    # First try multiline format with |
-    hint_match = re.search(r"^argument-hint:\s*\|\s*\n((?:  .+\n?)+)", frontmatter, re.MULTILINE)
+    # First try multiline format with | (supports empty lines)
+    hint_match = re.search(r"^argument-hint:\s*\|\s*\n((?:  .+\n?|\s*\n)+)", frontmatter, re.MULTILINE)
     if hint_match:
         # Remove leading indentation from multiline strings
         hint_content = hint_match.group(1)
@@ -325,11 +325,16 @@ def apply_translations_to_template(content: str, translations: dict) -> str:
         # Check if original hint is multiline (uses |)
         if re.search(r"^argument-hint:\s*\|", content, re.MULTILINE):
             # Build new multiline content with proper indentation
+            # Only add indentation to non-empty lines
             hint_lines = new_hint.split("\n")
-            indented_hint = "\n  ".join(hint_lines)
-            # Replace multiline hint - match the entire multiline block
+            indented_lines = [("  " + line) if line else "" for line in hint_lines]
+            indented_hint = "\n".join(indented_lines)
+            # Replace multiline hint - match the entire multiline block (supports empty lines)
             content = re.sub(
-                r"(argument-hint:\s*\|)\s*\n((?:  .+\n?)+)", rf"\g<1>\n  {indented_hint}\n", content, flags=re.MULTILINE
+                r"(argument-hint:\s*\|)\s*\n((?:  .+\n?|\s*\n)+)",
+                rf"\g<1>\n{indented_hint}\n",
+                content,
+                flags=re.MULTILINE,
             )
         else:
             # Replace single-line hint (with or without quotes)

{codexspec-0.5.0 → codexspec-0.5.2}/templates/commands/generate-spec.md

@@ -23,12 +23,33 @@ You are now acting as a "Requirement Compiler". Execute the following operations
 
 ### Steps
 
-1. **Determine Feature ID**: List directories in `.codexspec/specs/` using `ls` command to find existing spec directories (each spec is a directory named `{NNN}-{feature-name}/`). Determine the next sequential number (e.g., if `001-*` directory exists, use `002-`).
+1. **Determine Feature ID**: Generate a unique prefix using timestamp + random suffix:
 
-   > **IMPORTANT**: Do NOT use Glob to detect existing specs - Glob only matches files, not directories. Use `ls` or `Bash` tool instead.
+   ```bash
+   # Get current timestamp
+   TIMESTAMP=$(date +"%Y-%m%d-%H%M")
 
-2. **Create Feature Directory**: Create a new directory `.codexspec/specs/{NNN}-{feature-name}/` where:
-   - `NNN` is the sequential number (001, 002, etc.)
+   # Generate 2-character random suffix from [a-z0-9]
+   RANDOM_SUFFIX=$(head /dev/urandom | LC_ALL=C tr -dc 'a-z0-9' | head -c 2)
+
+   # Full prefix: 16 characters (e.g., "2025-0321-1430k7")
+   PREFIX="${TIMESTAMP}${RANDOM_SUFFIX}"
+   ```
+
+   **Format Specification**:
+   - `YYYY`: 4-digit year (e.g., 2025)
+   - `MM`: 2-digit month (01-12)
+   - `DD`: 2-digit day (01-31)
+   - `HH`: 2-digit hour (00-23)
+   - `MM`: 2-digit minute (00-59)
+   - `{random}`: 2 random characters from [a-z0-9] (36 characters, 1296 combinations)
+
+   > **Format**: `{YYYY-MMDD-HHMM}{random}-{feature-name}`
+   > **Example**: `2025-0321-1430k7-user-authentication`
+   > **Regex**: `^\d{4}-\d{4}-\d{4}[a-z0-9]{2}-[a-z0-9-]+$`
+
+2. **Create Feature Directory**: Create a new directory `.codexspec/specs/{YYYY-MMDD-HHMM}{random}-{feature-name}/` where:
+   - `{YYYY-MMDD-HHMM}{random}` is the 16-character unique prefix (e.g., `2025-0321-1430k7`)
    - `feature-name` is a kebab-case description of the feature
 
 3. **Generate spec.md**: Create a comprehensive specification document including:
@@ -46,7 +67,7 @@ You are now acting as a "Requirement Compiler". Execute the following operations
 
 5. **Auto-Review Generated Spec**: After saving the spec, automatically run the review process:
    - Execute the same quality checks as `/codexspec:review-spec`
-   - Generate a review report at `.codexspec/specs/{NNN}-{feature-name}/review-spec.md`
+   - Generate a review report at `.codexspec/specs/{YYYY-MMDD-HHMM}{random}-{feature-name}/review-spec.md`
    - If issues are found, present a summary and ask if user wants to fix them now or proceed
 
 ### Spec Template Structure
@@ -107,9 +128,9 @@ Before saving, verify:
 
 ### Output
 
-Save the specification to: `.codexspec/specs/{NNN}-{feature-name}/spec.md`
+Save the specification to: `.codexspec/specs/{YYYY-MMDD-HHMM}{random}-{feature-name}/spec.md`
 
-A review report will also be generated at: `.codexspec/specs/{NNN}-{feature-name}/review-spec.md`
+A review report will also be generated at: `.codexspec/specs/{YYYY-MMDD-HHMM}{random}-{feature-name}/review-spec.md`
 
 > [!IMPORTANT]
 > This command should be called after `/codexspec:specify` has clarified all requirements. It focuses on document generation, not requirement exploration.

{codexspec-0.5.0 → codexspec-0.5.2}/templates/commands/pr.md

@@ -71,7 +71,7 @@ By default, spec.md is **NOT** used. Use `--spec` to enable SDD workflow integra
 | Value | Behavior |
 |-------|----------|
 | (not specified) | No spec integration, generate from git only |
-| `001-auth` | Use `.codexspec/specs/001-auth/spec.md` |
+| `2025-0321-1430k7-auth` | Use `.codexspec/specs/2025-0321-1430k7-auth/spec.md` |
 | `path/to/spec.md` | Use specified spec.md file path |
 
 **When to use**:
@@ -121,10 +121,12 @@ Only when `--spec` is provided, read spec.md for Context section.
 
 ### Spec Resolution
 
-1. If `--spec` is a number like `001`, resolve to `.codexspec/specs/001-*/spec.md`
-2. If `--spec` is a directory name like `001-auth`, resolve to `.codexspec/specs/001-auth/spec.md`
+1. If `--spec` is a partial prefix like `2025-0321`, resolve to `.codexspec/specs/2025-0321*/spec.md`
+2. If `--spec` is a full directory name like `2025-0321-1430k7-auth`, resolve to `.codexspec/specs/2025-0321-1430k7-auth/spec.md`
 3. If `--spec` is a path, use directly
 
+> **Note**: Legacy sequential format directories (e.g., `001-feature`) are also supported for backward compatibility.
+
 ### Content Extraction (Best-Effort)
 
 Extract content from spec.md with priority order: