OttawaCloudConsulting
- 28 skills
- 0 followers
- 1 week ago last updated
- ▌ Project · ottawacloudconsulting bundleProject 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.
- ▌ Red Team · ottawacloudconsulting bundleAdversarial 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.
- ▌ Narrative · ottawacloudconsulting bundleWrite 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 · ottawacloudconsulting bundleGenerates 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".
- ▌ Create Prd · ottawacloudconsulting bundleCreate 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.
- ▌ Cdk Testing · ottawacloudconsulting bundleRun CDK validation, security scanning, build, test, and deployment. Use when the user asks to test CDK code, validate CDK configurations, run CDK checks, or deploy CDK to a dev environment. Triggers on requests like "test cdk", "validate my cdk", "run cdk checks", "deploy cdk to dev", or "/test-cdk". Handles TypeScript CDK projects with cdk.json and package.json. Do NOT use for CDK synth-only workflows, Python CDK projects, non-CDK TypeScript testing, or staging/production deployments.
- ▌ Daily Report · ottawacloudconsulting bundleWrite 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.
- ▌ Project Design · ottawacloudconsulting bundleExplicit 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.
- ▌ Plan Feature · ottawacloudconsulting bundlePer-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 Milestone · ottawacloudconsulting bundleExplicit 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.
- ▌ Nist Fedramp Assessment · ottawacloudconsulting bundleMap AWS project architecture to NIST SP 800-53 Rev 5 / FedRAMP Moderate security controls. Produces a phased compliance assessment (4 output documents) with AWS shared responsibility inheritance and risk-rated gap analysis. Use when asked to assess FedRAMP compliance, run a NIST 800-53 control mapping, check FedRAMP Moderate controls, evaluate FedRAMP posture, perform a NIST 800-53 assessment, or assess for FedRAMP ATO readiness. Do NOT use for NIST CSF assessments, ITSG-33 assessments, FedRAMP High or Low baselines, or non-AWS cloud environments.
- ▌ Over Engineering Review · ottawacloudconsultingOn-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.
- ▌ Project Plan Feature · ottawacloudconsulting bundleExplicit 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.
- ▌ War Discovery Interview · ottawacloudconsultingInteractive 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 · ottawacloudconsultingReads 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 · ottawacloudconsulting bundleGenerate 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.
- ▌ Spike · ottawacloudconsulting bundleAdversarial 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.
- ▌ Define · ottawacloudconsulting bundleCodebase 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.
- ▌ Design · ottawacloudconsulting bundleArchitecture 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.
- ▌ Itsg Assessment · ottawacloudconsulting bundleMap project architecture to ITSG-33 / CCCS Medium Cloud Profile security controls for Canadian GC cloud workloads handling Protected B data. Produces a phased compliance assessment with AWS control inheritance and risk-rated gap analysis. Use when asked to assess ITSG, run a CCCS Medium compliance check, evaluate Canadian cloud compliance, map ITSG-33 controls, perform a GC cloud security assessment, or check Protected B data handling requirements. Do NOT use for FedRAMP, NIST CSF, SOC 2, PBMM standalone reviews, TBS cloud profile assessments, or other non-ITSG-33 compliance frameworks.
- ▌ Architecture Doc · ottawacloudconsulting bundleProduce 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.
- ▌ Occ Skill Creator · ottawacloudconsulting bundleGuide for creating effective skills. Use when building a new Claude skill, packaging a domain workflow as a reusable skill bundle, or formalizing a repeated procedure. Covers the full lifecycle: creation, structured review, and iteration. Invoke explicitly with /occ-skill-creator.
- ▌ Milestone · ottawacloudconsulting bundleMilestone 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.
- ▌ Terraform Testing · ottawacloudconsulting bundleRun Terraform (and OpenTofu) validation, security scanning, planning, and deployment testing for .tf and .tfvars files. Use when the user asks to test Terraform or OpenTofu code, validate Terraform configurations, run Terraform checks, deploy Terraform to a dev environment, or test tofu configs. Triggers on requests like "test terraform", "validate my terraform", "run terraform checks", "deploy terraform to dev", "/test-terraform", "test opentofu", "validate my tofu", or "run tofu checks". Do NOT use for CloudFormation, Pulumi, CDK, or non-Terraform infrastructure code.
- ▌ Occ Skill Refactor · ottawacloudconsulting bundleReviews and refactors an existing skill against quality standards. Accepts a skill path (e.g. skills/<skill-name>/ or .claude/skills/<skill-name>/). Invoke explicitly with /occ-skill-refactor. Do NOT use to create a new skill from scratch.
- ▌ Project Spike · ottawacloudconsulting bundleExplicit 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.
- ▌ Nist Csf Assessment · ottawacloudconsulting bundleMap project architecture to NIST Cybersecurity Framework (CSF) 2.0 outcomes. Produces a phased assessment at the subcategory level with cloud service evidence mapping and NIST 800-53 informative references. Always uses the latest published CSF version. Use when asked to assess CSF compliance, run a NIST CSF mapping, check Cybersecurity Framework posture, evaluate CSF 2.0 controls, or perform a cybersecurity framework assessment. Do NOT use for general security audits, penetration testing, ITSG assessments, FedRAMP assessments, or standalone NIST SP 800-53 control assessments — use the dedicated skills for those frameworks.
- ▌ Project Define · ottawacloudconsulting bundleExplicit 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.