Add spec-driven product task workflow

[tom2drum]

Description and Related Issue(s)

Introduces a spec-driven workflow for working product tasks whose GitHub issues arrive underspecified (a title and a couple of links — e.g. #3537, #2909). The workflow fills the task's gaps through a structured interview, routes unanswerable questions to the responsible people via Slack, and executes the resulting spec one subtask at a time — explicitly separating what an agent may implement from what stays with a developer (final markup/styling against Figma mockups).

Entry point for the team: .agents/tasks/README.md.

Proposed Changes

• Three new skills:
  • grill-the-task — research-first interview: fetches the issue, explores the codebase, curls live API samples, enumerates Figma mockups; runs mockup↔API sufficiency and field-propagation cross-checks; then grills the developer one question at a time and front-loads the executor skills' inputs into the spec.
  • to-spec — converts any conversation into a spec in .agents/tasks/ (or merges into an existing one); sends open questions to their owners in Slack (channel-first for product questions, in Russian), harvests replies back into the spec, and bootstraps the branch + draft PR.
  • implement-task — executes the spec one leaf subtask per run, inferring the spec from the branch name (issue-<number> / issue-<number>-step-<N> / task-dir slug); hands [human] subtasks over to the developer.
• Supporting files: .agents/rules/delegation.mdc (living agent/human boundary, incl. the scaffold→style split and standing testing policy), .agents/TEAM.md (per-team contact roster + Slack routing channels), .agents/tasks/README.md (lifecycle doc), and the generic grilling interview skill promoted from a personal skill.
• create-pr skill reworked into three modes: placeholder draft PR at spec time, finalize-draft into ready-for-review, and the classic create-right-away flow. The dependencies label now requires changes in actual dependency sections of package.json, not scripts.
• Checks workflow: draft PRs are skipped (same gate as the skip checks label), checks run on ready_for_review, manual runs stay available via workflow_dispatch; .agents/** and .cursor/** added to paths-ignore.

No ENV variable changes.

Breaking or Incompatible Changes

None for the application. One CI behavior change: the Checks workflow no longer runs automatically on draft PRs — it runs when the PR is marked ready for review, and can always be triggered manually via workflow_dispatch.

Additional Information

Specs will accumulate in .agents/tasks/ (they merge together with their task's PR) and serve as precedent for future tasks. .agents/TEAM.md stores Slack member IDs deliberately — they are workspace-scoped identifiers, not credentials — to make question routing deterministic.

Checklist for PR author

• I have tested these changes locally.
• I added tests to cover any new functionality, following this guide
• Whenever I fix a bug, I include a regression test to ensure that the bug does not reappear silently.
• If I have added a feature or functionality that is not privacy-compliant (e.g., tracking, analytics, third-party services), I have disabled it for private mode.
• If I have added, changed, renamed, or removed an environment variable
  • I updated the list of environment variables in the documentation
  • I made the necessary changes to the validator script according to the guide
  • I added "ENVs" label to this pull request

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. To trigger a review, include @coderabbitai review in the PR description. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: ca001927-2e06-42db-8f55-1bf0d79cf655

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}