Skip to content

Integrate a .sdlc directory containing the software development lifecycle artifacts #1

Description

@tomzx

Background

The goal is to implement an agentic workflow for software development as described in the referenced Medium article. This involves creating a structured directory (.sdlc) that contains project context, templates, specifications, and knowledge artifacts to guide AI agents in software development tasks.

.sdlc/
  context/                        # Persistent project context
    project-overview.md           # What the system does, tech stack, scope
    architecture.md               # Architecture decisions and patterns
    conventions.md                # Naming, structure, coding standards
  templates/                      # Reusable artifact templates
    requirement-template.md
    task-template.md
  specs/                          # Per-feature specifications
    REQ-001-notification-system/
      requirement.md              # The spec
      tasks/
        TASK-001-implement-notification-service.md
        TASK-002-create-email-channel.md
  knowledge/              # Accumulated project knowledge & answered questions

src/                      # Source code (normal location)
tests/                    # Tests (normal location)
AGENTS.md                 # Root-level agent context

Acceptance Criteria

  • Create .sdlc directory in the repository root
  • Create context/ subdirectory with project-overview.md, architecture.md, and conventions.md files
  • Create templates/ subdirectory with requirement-template.md and task-template.md files
  • Create specs/ subdirectory for feature specifications
  • Create knowledge/ subdirectory for accumulated project knowledge
  • Ensure existing src/, tests/, and AGENTS.md remain in their normal locations
  • All created files should have appropriate placeholder content explaining their purpose
  • Update AGENTS.md to reference the new .sdlc structure if needed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions