Skip to content

Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-team-core-feature

saas-team-core-feature

Unverified

Orchestrate PM, backend, frontend, AI, and QA specialists to deliver a SaaS feature.

Running this workflow on this client

Run commands from the project root (use Git Bash on Windows if bash points to an unavailable WSL distro). Shared studio files live in .claude/; follow .agents/PORTABLE-RUNTIME.md and .claude/docs/config-resolution.md for client tools, delegation, and approval rules.

Run bash .claude/hooks/yaml-helper.sh resolve_config --keys locale,review_mode,automation and use its output below.

Resolved above — use as-is; --review overrides review_mode for this run.

Team Core Feature

Locale & User Profile: Match locale (pt-BR → natural Brazilian Portuguese questions/options, overriding English examples; en → English) and user_profile (founder → plain business language with (Recomendado) first, zero tech jargon; developer → technical). Keep code/tests in English.

Orchestrate the specialized engineering team to deliver a primary SaaS capability from concept through implementation and verification.

Argument check: If no core feature description is provided, output:

"Usage: /saas-team-core-feature [feature description] [--review full|lean|solo] — Provide a description of the core SaaS workflow or feature you want to build."

When this skill is invoked with a valid argument, orchestrate the team through a structured process:

  1. Design & Spec Phase:

    • lead-product-manager: Author PRD draft (production/core-features/[feature]-prd-draft.md)
    • backend-engineer: Technical architecture notes & DB schema impacts
    • frontend-engineer: UI state, component hierarchy, and responsive interaction spec
    • If AI-powered: ai-engineer: LLM prompt pipeline, context retrieval, tool schemas
  2. Cross-Discipline Alignment:

    • Resolve data contracts (API input/output schemas with Zod/Pydantic)
    • Ensure tenant isolation and auth permissions are respected
  3. Implementation Phase:

    • backend-engineer: Database migration, service logic, API endpoints (src/app/api/... or api/routes/...)
    • frontend-engineer: React/Next.js UI components, form hooks, optimistic updates
    • If AI-powered: ai-engineer: Streaming response handlers, embedding vector search
  4. Validation Phase:

    • qa-manual-tester: Integration test suite (Vitest/Pytest), E2E test scenarios (Playwright)
    • Verify acceptance criteria and error edge cases (empty states, rate limits, network failure)
  5. Closing Verdict:

    • Output: COMPLETE — core feature designed, implemented, and validated.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 321kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 321kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 321kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 197kUpdated Claude CodeCodexVerifiedInstall