OttawaCloudConsulting
@OttawaCloudConsulting
Public Skills
plan-feature
by OttawaCloudConsulting
Per-feature implementation plan with sub-feature sizing, interface contracts, and test commands. Supports re-plan mode for scope changes. Use when planning a feature, creating implementation plan, or re-planning. Phrases like "plan feature", "implementation plan", "re-plan feature", "create plan" are good triggers.
project
by OttawaCloudConsulting
Project orchestrator. Bootstraps progress.txt on first run, reports project state, and routes to the next skill on every subsequent invocation. Use when starting a new project, checking project status, or deciding what to do next. Phrases like "where am I", "project status", "what's next" are good triggers.
narrative
by OttawaCloudConsulting
Write the session narrative: the prose record of what a work session did, what it found, and what it did not prove, filed into DailyReports/narratives/YYYYMMDD-slug.md. Not a summary and not a changelog. A short argued account where the title is the finding, every section earns its place, and wrong predictions and declined review findings are recorded rather than dropped. Use at the end of any work session, and whenever the user says "write the narrative", "write this up", "narrative for today", "record what we did", "document this session", or asks for source material for the daily report or speaking notes. Also use to reconstruct a narrative for a past session from its artifacts.
workitems
by OttawaCloudConsulting
Generates a linked Epic, Feature, and Story work item document set for Jira, Azure DevOps, or any tracker, in an Epic > Feature > Story > Task hierarchy. Maps a project to an Epic, each milestone to a Feature, and each milestone feature to a Story, with parent references and source-artifact traceability in every document. Use this whenever the user mentions writing a feature, epic, or story, filing or drafting work items, a Jira ticket or issue, an Azure DevOps or ADO work item, a backlog or backlog item, an epic breakdown, or asks to turn a plan, PRD, or milestone set into something a delivery team can pick up, even when they do not name a tracker or say the words "Epic", "Feature", or "Story".
daily-report
by OttawaCloudConsulting
Write the daily status report into DailyReports/YYYYMMDD.txt, built from that day's session narratives, the git commits in this workspace's writable repositories, and the project artifacts under .project/. Defaults to today's date; given a past date (or context describing an earlier day) it reconstructs that day's report instead, from artifacts alone where no narrative exists. Four sections: Date, Today, Commits, WorkItems, Tomorrow. Translates every workspace-local planning identifier (milestone numbers, feature numbers, gate numbers, sub-feature markers) into descriptive text a reader outside this workspace can follow. Use whenever the user says "daily report", "write the report", "write up today", "EOD report", "status report", "what did I do today", or names a specific past date to report on, and use it as well when a session is wrapping up and a report for the day does not exist yet.
create-prd
by OttawaCloudConsulting
Create a PRD, architecture document, and progress file for a new project through guided interview. Use when starting a new project, planning a new feature, writing requirements, scoping a project, or creating project documentation from scratch. Phrases like "I want to plan a new project" or "help me write requirements for" are good triggers. Do NOT use for updating an existing PRD, documenting changes to an existing system, writing a technical design doc for an in-progress change, or starting implementation.
spike
by OttawaCloudConsulting
Adversarial technical research with red-team validation. Spawns research and red-team sub-agents to investigate technical questions and produce structured spike artifacts. Supports follow-up research on existing spikes. Use when investigating technical feasibility, comparing approaches, or validating assumptions before committing to a plan.
over-engineering-review
by OttawaCloudConsulting
On-demand active pass that runs the 3-clause discriminator over the current diff, a named file, or a plan/design doc and reports classified findings (safe-remove / needs-decision / keep / harmful-theater). Thin wrapper that composes /simplify and /code-review, adding only the requirement-ledger freeze and discriminator. Use when asked to "/over-engineering-review", "check for over-engineering", "run the discriminator", "gate this for YAGNI/KISS", or "is this over-engineered". Accepts optional target: diff (default) <file path> plan.
build
by OttawaCloudConsulting
Sub-feature-by-sub-feature implementation from Gate 4-approved plans. Refreshes codebase assessment, implements code, tracks deviations, runs tests, and updates state files. Supports multi-session builds via auto-resume. Use when implementing a feature, building code, or continuing a build session.
milestone
by OttawaCloudConsulting
Milestone breakdown from approved PRD and architecture doc. Supports defining milestones one at a time and revision mode for scope changes. Use when planning milestones, breaking work into milestones, or revising an existing milestone. Phrases like "define milestones", "milestone planning", "break into milestones", "revise milestone" are good triggers.
design
by OttawaCloudConsulting
Architecture and design specification from an approved PRD, with in-session revision before gate approval. Supports refresh mode to consolidate architectural deviations. Use when designing architecture, creating design doc, reviewing technical choices, or refreshing architecture after implementation deviations. Phrases like "design the architecture", "create design doc", "refresh architecture" are good triggers.
define
by OttawaCloudConsulting
Codebase assessment, optional Working Backwards, and PRD creation in a single session. Runs Gates 0, WB, and 1 continuously. Use when starting project definition, creating a PRD, assessing an existing codebase, or running the Working Backwards exercise. Phrases like "define the project", "create PRD", "assess codebase", "working backwards" are good triggers.
project-design
by OttawaCloudConsulting
Explicit Project design phase. Produces or refreshes docs/ARCHITECTURE_AND_DESIGN.md from an approved PRD and records Gate 2. Use only when the user explicitly invokes $project-design.
project-milestone
by OttawaCloudConsulting
Explicit Project milestone phase. Defines one milestone at a time from an approved PRD and architecture document, updates milestone artifacts, and keeps Gate 3 in progress. Use only when the user explicitly invokes $project-milestone.
project-build
by OttawaCloudConsulting
Explicit Project build phase. Implements a planned feature sub-feature by sub-feature, records deviations, runs the feature test command, and updates milestone-status.txt then progress.txt. Use only when the user explicitly invokes $project-build.
project-plan-feature
by OttawaCloudConsulting
Explicit Project feature planning phase. Produces or revises one Gate 4 feature implementation plan and updates only milestone-status.txt. Use only when the user explicitly invokes $project-plan-feature.
project-spike
by OttawaCloudConsulting
Explicit Project spike phase. Performs adversarial technical research, writes spike docs under docs/spikes, supports follow-ups, and tracks spike state in progress.txt. Use only when the user explicitly invokes $project-spike.
project
by OttawaCloudConsulting
Project orchestrator for explicit use only. Bootstraps progress.txt, reports project state, validates existing Project artifacts, and recommends the next Project skill. Use only when the user explicitly invokes $project or asks to use this skill for project status/routing.
project-define
by OttawaCloudConsulting
Explicit Project definition phase. Runs Codebase Alignment, optional Working Backwards, and Scope Review gates while producing docs/codebase-assessment.md, docs/working-backwards.md, and prd.md. Use only when the user explicitly invokes $project-define.
architecture-doc
by OttawaCloudConsulting
Produce or audit docs/ARCHITECTURE_AND_DESIGN.md for any codebase, standalone from the /project flow. Create mode reverse-engineers an architecture document from source for repos that lack one; Audit mode updates an existing document in place against the current code. Use when there is no architecture document and one is needed, when an existing architecture doc has drifted from the code, or when the user asks to "document this architecture", "reverse engineer the architecture", "create an architecture doc", or "audit the architecture doc against the current code". Operates on the current working directory by default; accepts an optional positional target_path argument.
red-team
by OttawaCloudConsulting
Adversarial review of any artifact -- code, designs, PRDs, architecture docs, or proposals. Spawns parallel sub-agents with different adversarial lenses to find flaws, gaps, and risks. Use when asked to red-team, critique, challenge, or adversarially review work. Triggers on "red-team this", "find holes in", "challenge my design", "what could go wrong", or "/red-team". Do NOT use for general code review, proofreading, style feedback, or non-adversarial review.
war-discovery-interview
by OttawaCloudConsulting
"Interactive interview to gather solution requirements for AWS Well-Architected Review. Conducts a structured interview covering business objectives, workload characteristics, compliance, performance, security, and cost. Produces DESIGN_REQUIREMENTS.md."
war-governance-profiler
by OttawaCloudConsulting
"Reads docs/TENANT_PROFILE.md and produces a WAR-specific governance baseline. Maps tenant-level controls (SCPs, guardrails, centralized services, compliance baselines) to the 6 AWS WAF pillars. Identifies inherited controls vs workload responsibilities. Uses AskUserQuestion to resolve gaps."
rule-creator
by OttawaCloudConsulting
Generate new rules — always-on behavioral guidelines for Claude Code. Use when asked to create a rule, write best practices, add a new rule file, or generate coding guidelines. Walks through an interactive interview to produce a rule file and its documentation. Do NOT use for auditing, reviewing, or listing existing rules.