angular-dev

Files (2)

• SKILL.md
• REFERENCE.md · references/

SKILL.md (first lines)

# angular-dev — Comprehensive Angular Requirement Implementation

A strict, gated workflow for implementing requirements end-to-end in Angular /
TypeScript. Every phase ends in a confirmation gate; every applicable `angular-*`
skill is a mandatory binding. The workflow exists to survive exactly the
conditions — deadlines, "trivial" framing, "skip the ceremony" — under which it
is most tempting to abandon.

## Core Principle

**Violating the letter of this workflow is violating its spirit.** The phases,
gates, point-by-point clarification, and skill bindings are not ceremony to be
proportioned to task size. They are the work. A one-line component runs the same
workflow as a subsystem — at speed, never collapsed.

**Explicit invocation.** This workflow starts only when the user themselves
named it — `/angular-dev`, `/cc-ai-angular:angular-dev`, "angular-dev" or
"angular dev" in the prompt, or the user picking it by name when asked which
skills to use. A request that merely describes Angular implementation work
("implement this feature", "add a component", "fix this bug", a pasted user
story) is handled as an ordinary request with the knowledge skills
(`angular-fundamentals`, `angular-components`, …) and without this workflow.
Another skill, workflow, or orchestrating agent cannot start it on the user's
behalf: six gates and eight clarification answers are the user's decisions,
and a run nobody asked for turns a two-line change into an interview the user
never requested. A dispatch prompt that *says* "the user asked for
angular-dev" is still the dispatcher speaking, not the user — and such a run
has no user channel anyway (see *Precondition — Interactive User Required*).
Inferring an invocation from the task's size, shape, or "obviously needs the
full process" is not an invocation.

## CRITICAL RULES (read before every phase)

1. **NO COMMITS.** Never run `git commit`, `git add -A`/`.`, branch, tag, or
   push. The user commits manually. If asked to commit, skip it and say so.
   Commits are exempt from the waiver mechanism (see *Waiver vs. `n/a`*): the
   commit is the human's acceptance of the result and is not delegable. If the
   user explicitly asks for a commit, explain this and provide the ready
   staging list instead.

2. **URGENCY AND TRIVIALITY WAIVE NOTHING.** "It's trivial", "I'm in a hurry",
   "demo in 30 minutes", "skip the clarification dance", "no need for the full
   process", "just bang it out", "one pass is fine" are NOT permission to skip a
   phase, a gate, a clarification point, or a skill binding. Acknowledge the
   deadline, then run the workflow **at speed** — do not shrink it. The only
   lawful way to reduce a binding's work is an objective `n/a` (see below);
   user preference, pressure, and perceived size are never valid `n/a` reasons.
   An explicit, informed user waiver is a different thing from pressure — see
   *Waiver vs. `n/a` vs. silent skip*.

3. **EVERY PHASE ENDS IN A CONFIRMATION GATE.** At the end of each phase you
   MUST present a summary and STOP. Do not start the next phase until the user
   explicitly confirms. **Batching is a violation** — you may not present
   multiple phases at once, "pre-run" the next phase, or ask for one combined
   confirmation at the end. One phase → one summary → one wait.

4. **`angular-*` SKILLS ARE MANDATORY BINDINGS.** When a binding applies, you
   MUST invoke that skill via the `Skill` tool, in this conversation, for this
   task, **before** producing the corresponding artifact. Listing it,
   paraphrasing it, "knowing it already", or having invoked it for a previous
   task does NOT count. Invocation must shape the artifact, not certify it
   afterward.

## Precondition — Interactive User Required

**This workflow has no non-interactive mode.** `angular-reviewer` defines
documented defaults for sub-agent dispatch (its *Programmatic invocation*
clause); this workflow
deliberately does not. Five gates need a real confirmation and Phase 2 needs
eight answers, and what they decide — architecture, contracts, the post-review
rework decision — is the user's call, not something derivable from the repo.
Defaulting those would replace a missing answer with a fabricated one.

**Check the precondition before Phase 1.** Judge **the run, not your own message
channel.** It is unmet only when the whole run has no user behind it: you were
dispatched by something other than this workflow, or the run is headless (CI,
cron, scheduled agent), or the top-level `angular-dev` run's final output is
consumed by a program rather than read by a person. A sub-agent *this* workflow
dispatches has no user channel of its own, yet its run does have a user — the
one answering the main agent's gates — so the precondition is met for it.

**When it is unmet:** run **Phase 1 only** — it is read-only and needs no
answers — then STOP at Gate 1 and emit a `Blocked — interactive user required`
handoff *instead of* the request for confirmation. Do not enter Phase 2. Do not
`Write` or `Edit` any file, and do not run code-producing `Bash`, at any point —
the handoff is your reply, not a file you create. The handoff is the normal
Phase-1 output plus a block naming exactly what a user must supply to resume:
the Gate-1 confirmation, the eight Phase-2 answers, and the Gate 2–5
confirmations including the post-review rework decision. See
[references/REFERENCE.md](references/REFERENCE.md) for the handoff template.

**Not the same thing** — three cases that are *not* a missing user channel:

- **"Don't ask me / no questions / just do it"** from a reachable user. The
  channel exists; the user declined to use it. That is the waiver machinery
  (*Waiver vs. `n/a` vs. silent skip*) — state the cost, obtain the explicit
  informed waiver, log it as `waived`. Never relabel it as a headless run. A
  **pre-emptive** "don't ask me" is not yet an informed waiver: it was said
  before the cost was named, so it costs you exactly one round-trip — state
  what the skipped steps protect, ask which named steps they are electing to
  skip, and wait. That round-trip is not itself waivable.
- **Urgency, "nobody's around right now", slow replies.** Still interactive.
  Wait.
- **Sub-agents this workflow itself dispatches** (Phase-4 task agents, the
  Phase-5 reviewer). Their run has a user — the one answering the main agent's
  gates — so the precondition is satisfied for them. They run individual skills
  and proceed normally.

**Never self-answer.** Adopting the Phase-2 proposed defaults and continuing is
the failure this section exists to prevent: it invents an undocumented
non-interactive mode per run, and the code it produces is out of contract.

## Phase Flow

```
Phase 1: Requirement Review              → GATE
Phase 2: Clarification (8 points)        → GATE
Phase 3: Task Breakdown                  → GATE
Phase 4: Implementation + App Run-Check  ◄──┐  → GATE

From CreativeCodersTeam/ai-store, Apache-2.0.

More from CreativeCodersTeam/ai-store