[Fernando de Oliveira (fedeoliv)]

Discussion Link

Link: No linked discussion. This change addresses #37.

Context

Generated task titles can include sequential identifiers such as T-1 even though the board already provides its own identity. Agents also add invented codes throughout documents, making them denser and harder to follow.

Closes #37

Solution

• Add shared guidance favoring descriptive names and links over invented identifiers in newly written or rewritten content.
• Exclude sequential task and story prefixes from generated GitHub and Azure DevOps titles, with examples and a pre-creation check in decomposition.
• Add a task-quality check while preserving feature prefixes, meaningful domain numbers, native board IDs, hierarchy, and dependency links.
• Update repository instructions, distributed instruction templates, published documentation, and the changelog.
• Preserve existing documents and references without automatic cleanup or renaming existing board items.

Scope boundary: this is the first slice of the broader readability work. Spec templates and ID-dependent implementation and verification contracts remain unchanged. Removing mandatory spec identifiers requires a coordinated follow-up, with continued support for existing numbered specs.

Validation:

• npm --prefix docs run build: passed, 39 pages built.
• git diff --check: passed.
• git diff --cached --check: passed before commit.
• markdownlint --stdin --json --config .markdownlint.yaml: run for each changed file and its HEAD baseline. Baseline comparison passed with zero new diagnostics after accounting for shifted line numbers. Existing lint diagnostics remain unchanged.
• bash .github/plugins/devsquad/hooks/sdd-init.sh verify: completed successfully before and after the change. Outputs match exactly, including pre-existing customized-file drift and four missing artifact templates. This does not indicate that every managed file is up to date.

Consumer adoption: update the plugin and apply the naming guidance to existing instruction files, or preview sdd-init.sh update-all --dry-run and review planned overwrites before applying template updates.

Checklist

• Linked discussion exists
• Solution has been validated