Skip to content

feat(ai-project-generator): conditional sprints, UX platform awareness & priority fix#202

Merged
parth0025 merged 1 commit into
stagingfrom
feat/ai-project-plan-conditional-sprints-v2
Jun 1, 2026
Merged

feat(ai-project-generator): conditional sprints, UX platform awareness & priority fix#202
parth0025 merged 1 commit into
stagingfrom
feat/ai-project-plan-conditional-sprints-v2

Conversation

@parth0025

@parth0025 parth0025 commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Conditional sprint additions β€” three new sprint/task groups injected into the AI plan prompt; each is skipped automatically when its condition is not met
  • UX design platform awareness β€” clarify step asks which design tool the team uses; plan generates a platform-specific setup task with step-by-step instructions (incl. Figma MCP server)
  • Priority fix β€” removed Urgent, enforced Low / Medium / High only (company defaults), added distribution-check rule to stop the model over-assigning High

Files changed (6)

File Change
prompts/project-plan/special-sprints-guidance.md New. Three conditional additions: GitHub setup, tech-stack + design platform setup, test case guidelines
promptBuilder.js Wires new partial between sprint-guidance.md and task-guidance.md
prompts/clarify/system.md Adds design platform question + dimension-scan row
prompts/project-plan/task-guidance.md Priority: Low/Medium/High only + required distribution check
prompts/project-plan/schema.md Priority enum drops Urgent
orchestrator.js PRIORITY_NORMALIZE drops urgent, falls back to MEDIUM

Conditional additions detail

Sprint Condition Contents
GitHub & Version Control Setup Source code or multi-dev 8 tasks: account/org, repo, SSH/HTTPS auth, branching strategy, commit & PR conventions, branch protection, semantic versioning
Environment & Tech-Stack Setup Any item needing install/config One task per item; includes per-platform UX design setup (Figma MCP, Penpot, Adobe XD, Framer, Sketch, Balsamiq, Miro)
Test Case Guidelines 2+ testable modules 4 tasks: what test cases are, how to write them, module-wise structure, QA tracking

Test plan

  • Software project β†’ GitHub sprint first, tech-stack sprint second, test case sprint third
  • Content/podcast project β†’ none of the three conditional sprints appear
  • Clarify step for a project with screens β†’ design platform question appears
  • Figma selected β†’ Figma MCP setup task present in setup sprint
  • Task priorities β†’ no Urgent, High used sparingly (~1–2 per sprint)

πŸ€– Generated with Claude Code

…s, and priority fix

== 1. Conditional sprint additions (promptBuilder.js + special-sprints-guidance.md) ==

New prompt partial injected between sprint-guidance and task-guidance:

- GitHub & Version Control Setup sprint (first sprint when source code or
  multi-dev is detected): 8 step-by-step tasks covering account/org setup,
  repo creation, SSH/HTTPS auth, branching strategy, commit conventions,
  PR conventions, branch protection, semantic versioning + changelogs.

- Environment & Tech-Stack Setup sprint (one task per qualifying tech item):
  databases, backend frameworks, cloud services. Each task covers install,
  configure, create instance/DB, verify connection.

- Test Case Guidelines sprint (when project has 2+ testable modules):
  4 tasks covering what test cases are, how to write them, module-wise
  structure mapped to the project's own modules, and QA tracking workflow.

All three are conditional β€” omitted when the condition is not met.

== 2. UX design platform awareness (clarify/system.md + special-sprints-guidance.md) ==

Clarify step now asks which design/UX tool the team will use whenever
the project involves screen design or wireframing. Options: Figma,
Adobe XD, Penpot (open-source), Framer (code-based), Sketch (macOS),
Balsamiq (low-fidelity), Miro, Let AI decide.

Plan generation emits a platform-specific setup task for the chosen
tool, including Figma MCP server setup (token generation, npx install,
config JSON, benefits for design-to-code handoff with AI assistants).

Fixed: design tools were wrongly listed in the skip list for tech-stack
setup β€” they now correctly qualify as setup items.

== 3. Priority fix (task-guidance.md + schema.md + orchestrator.js) ==

- Removed Urgent entirely. Only Low / Medium / High are valid β€” these
  are the three default priority values in every AlianHub installation.
- Added required distribution check: if >1/3 of tasks are High the model
  must go back and downgrade; expected ratio is ~1-2 High, 4-6 Medium,
  1-2 Low per sprint.
- schema.md enum updated: "Low" | "Medium" | "High" (no Urgent).
- orchestrator.js PRIORITY_NORMALIZE map drops urgent; any stale value
  falls through to the MEDIUM default.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@parth0025 parth0025 merged commit 784e6dd into staging Jun 1, 2026
1 check failed
@parth0025 parth0025 self-assigned this Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant