Nicolás Schmidt
Community@nico0695
Nicolás Schmidt builds spec-driven development and blueprint-analysis skills covering proposal, design, execution, code review, QA, and git conflict resolution.
Agent Skills by Nicolás Schmidt
Showing 45 vetted skills indexed across 1 GitHub repositories.
nico0695slack-feature
Implements new Slack commands and event handlers in a TypeScript Slack bot project.
nico0695new-module
Scaffolds layered TypeScript feature modules with controllers, services, repositories, and Jest tests.
nico0695rest-endpoint
Adds REST API endpoints to Express web controllers with auth decorators and tests.
nico0695sddl-eval-level-3
Runs the sdd-lite main orchestration flow end to end in a disposable fixture with human approval gates.
nico0695sddl-eval-level-2
Runs provider-native behavioral probes evaluating sdd-lite triggers, routing, and session isolation.
nico0695sddl-eval-report
Rebuild sdd-lite evaluation reports and compare candidate runs against named baselines.
nico0695sddl-eval-level-1
Runs deterministic structural integrity checks against an installed sdd-lite workspace.
nico0695sddl-eval-init
Initializes a local sdd-lite-evals workspace for a project and active CLI provider.
nico0695sddl-eval
Routes users to the appropriate sdd-lite evaluation level based on testing goals.
nico0695sdd-spec
Writes behavior specifications with acceptance criteria for spec-driven development changes.
nico0695project-map-init
Generates a canonical project map file capturing stack, structure, and conventions for SDD workflows.
nico0695sdd-archive
Archives verified SDD change folders into a dated archive tree with closure reports.
nico0695sdd-apply
Executes approved SDD task batches as controlled code changes with checkpoints.
nico0695sdd-verify
Validates implemented changes against specs and tasks, producing an evidence-backed verify report and verdict.
nico0695skill-registry
Generates the canonical SDD v2 skill registry and compact session rules.
nico0695sdd-explore
Inspects repository context and writes an explore.md discovery artifact for spec-driven development.
nico0695stage-qa
Runs incremental batch-scoped quality checks after code-touching apply batches in SDD v2.
nico0695doc-writer
Generate grounded technical Markdown documentation from session context, code, and source files.
nico0695commit-closer
Generate commit messages and PR descriptions from git diffs and commit ranges.
nico0695code-review
Reviews code changes in diffs, commits, and branches with evidence-based findings and suggested fixes.
nico06954r-review
Reviews code diffs using a risk-tiered four-lens protocol with corroboration and optional ledgers.
nico0695judgment-day
Runs two blind independent reviews of code or documents and merges findings by convergence.
nico0695grill-me
Interviews the user in rounds to surface and resolve open decisions in a plan.
nico0695sddl-proposal
Generates a lightweight proposal.md framing problem, scope, and feasibility for spec-driven changes.
Frequently Asked Questions About Nicolás Schmidt
FAQPage SchemaWhat tasks can I accomplish with nico0695's skills?▼
You can run a full spec-driven change lifecycle (proposal, spec, design, plan, execution, QA, archive), perform read-only codebase analysis and architecture strategy via blueprint-harness, draft commit messages and PR descriptions, build throwaway prototypes, draft stakeholder questionnaires, and resolve git merge or rebase conflicts.
Who are these skills designed for?▼
Software engineers and technical leads who want structured, approval-gated development changes. The sdd-lite stages suit developers formalizing work into specs and plans, while blueprint-harness workers serve those needing read-only feasibility analysis, architecture alternatives, and RFC or bug-report exports.
How do I install and start using these skills?▼
Run sddl-init to bootstrap or refresh sdd-lite in your project, or bp-init to install blueprint-harness into a target repo, which copies the engine to .bp-harness/, seeds bp-workspace templates, and installs skills into detected AI setups. Orchestrators then trigger stages automatically.
Do these skills modify my repository or run git commands?▼
Mostly no. Blueprint-harness analysis workers are strictly read-only and write nothing; only bp-doc-exporter writes final artifacts. The merge-conflict skill reads git freely but never runs git write commands, and sddl-delivery drafts commit messages without executing git.
What prerequisites or dependencies do these skills require?▼
You need a project repository where sdd-lite or blueprint-harness can be bootstrapped via their init skills. sdd-lite stages depend on prior artifacts (proposal.md feeds spec.md, design.md feeds plan.md), and blueprint-harness requires its orchestrator to delegate phases to read-only workers.