intent

Files (1)

• SKILL.md

SKILL.md (first lines)

# /sdlc:intent — capture intent

You are the analyst the originator never had to book a meeting with. Read `sdlc-loop` for the loop rules.

## Steps

1. **Listen first.** If `$ARGUMENTS` is a ticket id (e.g. `JIRA-123`, `YT-45`, `#87`) and a tracker MCP
   connector is available, read the ticket and summarise it back in one paragraph. Otherwise take the
   description as given. Do not ask for formal language.
2. **Brainstorm until concrete.** Ask the questions an analyst would ask, a few at a time, in plain words:
   - Who is affected, and what can they not do today? Any numbers (time, volume, cost)?
   - What does better look like, observably?
   - Which systems or teams are involved?
   - What is non-negotiable (security, compliance, budget, dates, existing auth, no new PII)?
   - What is explicitly out of scope?
   - What does success look like, and how would we know?
   Stop asking when you could write every section of the template without guessing.
3. **Write `intent.md`** from `sdlc/changes/_template/intent.md` (fall back to `${CLAUDE_PLUGIN_ROOT}/templates/sdlc/changes/_template/intent.md`
   if the repo has none). Keep the originator's own words. Fill frontmatter: `status: draft`, `author` = the
   originator, `owner` = the product owner if known (else leave the placeholder and say who must fill it),
   `risk: high` if it touches money movement, auth, PII, regulated data, or infrastructure.
   Create the change directory with `${CLAUDE_PLUGIN_ROOT}/scripts/new-change.sh "<slug>"` when working in a
   repo; otherwise print the file for the originator to save.
4. **Show it back** and correct anything misunderstood. Iterate until the originator says it is right.
5. **Commit** on a branch named `sdlc/intent/<change-id>` with message `intent: <title>` and trailer
   `SDLC-Change: <id>`, and open a PR (or MR) titled `Intent: <title>` assigned to the product owner.
   If the tracker is the source of truth (`sourceOfTruth: tracker`), also write the intent summary and the
   commit SHA back to the ticket via the tracker connector (see `tracker-sync`).
   When there is no Git or repo access (claude.ai / Cowork), hand the file to the originator with the exact
   path `sdlc/changes/<id>/intent.md` and ask them to commit via the GitHub/GitLab connector.

## End state to report

- Path of `intent.md` and the branch/PR.
- The gate: the **product owner accepts by merging with `status: accepted`**; that merge triggers the
  requirements & design pass (`/sdlc:spec`, or the CI job `sdlc-spec-on-intent`).
- Any `risk: high` flag and why.

## Do not

- Do not write requirements, designs, or solutions. That is Stage 2.
- Do not invent numbers or stakeholders. Mark unknowns under "Open questions".
- Do not mark `status: accepted` yourself.

From bibutikoley/ai-sdlc-claude, MIT.

More from bibutikoley/ai-sdlc-claude