Capafy logo Capafy
はじめる
One Man Company Software Development Life Cycle

One Man Company Software Development Life Cycle

by: Dennis Wong
Run a full virtual product team from chat: PM → SA → Coder → QA → DevOps → Marketing. @mention roles, TASK-NNN tickets, and gated SDLC stages from backlog to deployed — built for solo founders who need a shippable process without hiring.
#生産性
評価
さらに評価が必要です
販売数
0
利用方法
ダウンロード

One Man Company Software Development Life Cycle

Ship like a product org — without hiring one.

You are the Boss. This Agent runs a virtual SDLC team in chat: PM → SA → Coder → QA → DevOps → Marketing, with @mentions, TASK-NNN tickets, and gated stage keywords from backlog to deployed → done.

Built from a real One Man Company workflow used to coordinate agents in Discord topic channels (#product, #engineering, #marketing, #support, #standup).

image.webp

Who this is for

  • Solo founders / indie hackers shipping a SaaS alone
  • Builders who want a repeatable process, not one-off chatbot answers
  • Teams that want SDLC discipline (tickets, gates, handoffs) inside chat

What you get

Role What it does
@PM Clarifies goals, creates TASK-NNN, prioritizes, closes the loop
@SA Specs, scope, acceptance criteria, risks
@Coder Implements or produces a file-level plan + verification steps
@QA Tests against AC; gates with qa verified / qa failed
@DevOps Deploy notes, version, rollback, reports deployed
@Marketing Launch copy after ship (no fake engineering status)
@Standup Digests status without moving the board

Happy path (canonical stages)

backlog → todo → in progress → in review → qa review → qa verified → ready to deploy → deployed → done

Roles may only move statuses they own (e.g. Coder never marks done or deployed). That keeps the board honest.

How to use (30 seconds)

  1. Paste a goal, optionally start with @PM.
  2. Answer only the clarifying questions that matter.
  3. Watch the Agent walk the chain with @Role: handoffs and exact status keywords.
  4. Ask @Standup anytime for a digest.

Example prompt

@PM I want password reset via email for my SaaS. Existing JWT auth. No SMS.

Example outcome

  • PM creates TASK-012, status todo, hands to @SA
  • SA returns scope + acceptance criteria, hands to @Coder / @QA
  • Coder summarizes implementation / plan, status in review
  • QA runs AC → qa verified / ready to deploy
  • DevOps reports deployed with version + rollback
  • PM summarizes for Boss → done (optional Marketing draft)

Topic rooms (logical)

Topic Use for
#product Roadmap, ideas, prioritization
#engineering Spec → code → QA → deploy
#marketing Launch / GTM
#support Bugs & customer issues
#standup Digests

Work stays in context — agents hand off with @Role: lines; you do not need role-named channels.

Why it works

  • Process, not vibes — every stage has an owner and a keyword
  • Self-contained handoffs — next role gets goal, constraints, and TASK id
  • No standby spam — never @Coder: wait for SA (prevents racey parallel turns)
  • Boss-facing close — PM always returns a human summary when work is done

Works on Capafy with zero Discord setup

Run Online: use this Agent in Capafy chat immediately.
(Optional later) The same methodology powers a self-hosted Discord/Telegram multi-bot stack for founders who want persistent channels — Capafy itself needs no bot tokens to try the Skill.

What this Agent will not do

  • Skip QA for production behavior changes
  • Invent ticket progress you never confirmed
  • Mark deployed / done from the wrong role
  • Require Jira/Discord credentials just to get value in-chat

Suggested first runs

  1. New feature — @PM + one sentence product idea
  2. Bug — paste repro steps; start in #support style with @PM or @SA
  3. Release note — after a simulated deployed, ask @Marketing for launch copy
  4. Weekly digest — @Standup what shipped and what’s blocked?

Author: wong ka ming
Skill: omc-sdlc · One Man Company SDLC methodology


View more