Skip to content

[Feature Request] Add Role-Based Spec Sections for Stakeholder Participation #41

@kanfil

Description

@kanfil

Summary

Add role-based sections in specs to differentiate contributions from Product, Architecture, and Engineering stakeholders.

Problem

InfoQ article emphasizes: "Different stakeholders participate differently" - Product (what/why), Architect (technical approach), Engineer (task execution).

Proposal

1. Role Markers in Specs

Add explicit sections:

  • Product Perspective: Business value, user stories, acceptance criteria
  • Architecture Perspective: Technical decisions, constraints, patterns
  • Engineering Perspective: Implementation tasks, test strategy

2. Role-Specific Templates

  • Opt-in template variants for different stakeholders
  • Guidance on who approves what in workflow

3. Stakeholder Views

  • Commands to filter/specify view (e.g., /spec.plan --stakeholder product)

Priority

Medium - Aligns with InfoQ enterprise patterns

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions