FDE FieldOps Skill Suite

    1

    A specialized FDE skill suite for stress-testing client requirements and enforcing architectural decision persistence.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    FDE FieldOps Skill Suite

    Example session with this skill installed

    The client wants to add a new SSO login button for their internal dashboard. Let's grill this request and document the constraints.

    • Read your context and instructions
    • Compiled the fde fieldops suite

    I have initiated the FDE discovery process for the SSO integration request. I am checking existing constraints in the memory system and will now proceed with the grilling interview across the 6 Pillars.

    FDE Discovery: SSO Integration Stress-Test

    To ensure this deployment doesn't hit a wall with the client's InfoSec or networking team, please provide specifics on these points:

    Authentication & Identity: Is this strictly OIDC/SAML, or is there a legacy IdP involved (e.g., ADFS)? Do we need to handle custom attribute mappings for x-org-id or specific role-based access control (RBAC) claims?
    2.

    Network & Host Boundary: Since the dashboard is in a customer VPC, will the IdP traffic require a new Egress Proxy rule or a PrivateLink to reach the identity provider?
    3.

    Security Veto Points: Does their Infosec policy allow for SP-initiated SSO, or are they mandating IdP-initiated only? What specific IAM roles must be provisioned for the callback service?

    Drafting Glossary Terms:

    "The Hub": Identified in initial notes. Need to confirm if this refers to the central Auth gateway or the application load balancer.

    Next steps

    1. Define the In-Scope vs. Out-of-Scope boundaries for the CLIENT_SPEC.md.
    2. Run python scripts/fde_core.py get-context --client "acme-corp" --keys "auth,infrastructure" to verify if current VPC settings allow public OIDC endpoints.
    3. Log the final SSO provider decision to the audit trail once the grilling phase is complete.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Client engineering projects fail when vague requirements meet rigid infrastructure. This skill suite provides a rigorous framework for Forward Deployed Engineers (FDEs) to stress-test client requests and maintain a deterministic memory of architectural decisions. It prevents scope creep and architectural drift by forcing interrogation of every deployment across six critical pillars.

    What it does

    • Stress-test requirements by interrogating client requests using Socratic discovery to uncover hidden infrastructure and compliance hazards.
    • Enforce decision persistence using a structured CLI-backed memory system that prevents contradictory architectural choices across sessions.
    • Model client domain glossaries to align engineering teams and stakeholders on company-specific jargon and technical definitions.
    • Generate auditable scope contracts that define explicit non-goals, failure policies, and InfoSec pre-requisites for sign-off.
    • Detect architectural conflicts by verifying new proposals against historical constraints before any code is written or manifests are changed.
    • Automate handoff packages producing unified summaries of decision audit logs and machine-readable state for project transitions.

    How it works

    1. Initialize client profiles using init-client to set baseline infrastructure, auth, and data residency constraints.
    2. Execute the grilling interview to resolve ambiguities in new feature requests across networking, identity, and security pillars.
    3. Verify architectural alignment using check-conflict to ensure new technical decisions do not violate established client boundaries.
    4. Finalize the scope contract by generating CLIENT_SPEC.md for stakeholder approval and logging the resulting decisions via the core CLI.

    Frameworks & tools

    The suite uses a Python-based core (fde_core.py) to manage structured YAML datastores. It integrates with standard Markdown for documentation and relies on CLI-driven context retrieval to maintain token efficiency.

    Why this beats prompting it yourself

    Generic prompts often result in "yes-man" behavior where the AI agrees to flawed architectures. This skill implements a specialized FDE methodology that treats every request as a potential deployment failure until proven otherwise. It replaces fuzzy memory with a deterministic audit trail, ensuring you never forget a client's specific VPC peering or data retention rules.

    Use cases

    • Pre-sales discovery to accurately scope integration efforts and identify "veto points" before signing contracts.
    • Architectural governance for long-running client engagements where multiple engineers rotate through the project.
    • Compliance-heavy deployments where air-gapped or sovereign region requirements must be strictly enforced.
    • Infrastructure migrations that require mapping legacy authentication flows to modern identity providers without downtime.

    Known limitations

    Requires a local Python environment to execute the fde_core.py scripts. Manual YAML editing is prohibited to maintain data integrity.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires local Python environment for the fde_core.py scripts. Does not support direct manual editing of YAML datastores. Context is scoped to specific clients to prevent data leakage.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    • Free with an Agensi account

    Software
    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This suite acts as a 'digital gatekeeper' that prevents project failure by stress-testing client requirements, maintaining a persistent memory of architectural decisions, and ensuring new requests don't conflict with established infrastructure constraints.

    The suite includes the Python-based core engine (fde_core.py), structured YAML datastores for memory persistence, documentation templates for scope contracts, and a specialized CLI for executing requirement 'grilling' interviews.

    Yes, it requires a local Python environment to run the core scripts; it is designed to work with any LLM-based agent capable of executing local CLI commands or interacting with a local file system.

    Unlike generic prompting, this skill uses a deterministic memory system and a Socratic discovery framework that actively challenges flawed logic rather than simply agreeing with user inputs.

    Updates are delivered via the marketplace repository, and because it uses a structured YAML-based data layer, your client profiles and historical decision logs remain compatible even as the core interrogation logic is refined.

    New in Agents & Orchestration

    Free