Requirement Compass
Extract goals, scope, constraints, and acceptance
I connect Skills, MCP, and specialist tools across requirements, engineering, documentation, and verification to create usable results.

Define outcomes, constraints, and acceptance
From codebase discovery and architecture to implementation, testing, and deployment, keeping requirements, implementation, test results, and final behavior aligned.
Using AI for scope, tasks, schedule, risks, quality, and acceptance so project materials are more complete and traceable.
Turning project material and technical experience into searchable, reusable assets for RAG, engineering collaboration, and continuous delivery.
Extract goals, scope, constraints, and acceptance
Break complexity into tasks, dependencies, priorities, and milestones
Understand structure, debt, and impact
Implement Java, Python, and TypeScript outcomes
Improve local structure while preserving behavior
Design interfaces, schemas, errors, and integration notes
Clean, transform, batch, log, and isolate exceptions
Build parsing, retrieval, citations, evaluation, and governance
Design instructions, context, formats, and robustness tests
Coordinate roles, parallel tasks, context, and integration
Connect structured context and callable tools
Navigate, read, act, and validate visible state
Connect local apps, scripts, screenshots, and UI automation
Create requirements, designs, technical documentation, SOPs, and project reports
Organize data, formulas, charts, and checks
Use screenshots, rendering, and diffs for UI acceptance
Design relevant tests and explain failures
Identify security, access, quality, dependency, and delivery risks
Turn progress, issues, decisions, and outcomes into management views
Capture learning as Skills, templates, scripts, and next inputs
Codebase and impact analysis
Web interaction and visible-state verification
Local application automation
Word and structured documents
Sheets, formulas, charts, checks
PDF generation and layout QA
Decks and management reporting
Original visuals and image work
Research and option comparison
Task, file, and delivery context
Model and business-service integration
Charts and interactive explanations
Connects local execution, code, and engineering tools so an Agent can move from analysis to action.
Connects developer knowledge and structured professional context for stronger solutions and decisions.
I avoid self-ratings and show real workflows, delivery scenarios, capability catalogs, and verification methods. Each item maps to a concrete action and usable output.
5-stage flow / Goals, context, roles, dependencies, and concurrency
20-item catalog / Domain rules, templates, scripts, and acceptance
2 channels / Runtime tools and structured knowledge context
Live UI checks / Page operations, visible state, scripts, and visual acceptance
3 delivery lanes / Engineering, documentation, tables, and visualization
4 check types / Builds, tests, rendering, data validation, and issue closure
These figures describe the current public workflow and catalog, not a rating, ranking, or external assessment.
Locate impact, implement incrementally, run relevant checks, and produce maintainable code and handoff.
Turn goals, scope, dependencies, risks, and acceptance into executable delivery structures.
Create and verify requirements, technical designs, project reports, SOPs, and knowledge documentation.
Handle sheets, logs, batch work, and repetitive flows with clear status, exception handling, and result checks.
Synthesize authoritative research, compare options, and produce clear recommendations.
Confirm delivery quality through builds, tests, screenshots, rendering, and diff checks.
Clarify the problem and desired result so every Agent action supports delivery.
Use clear context and reliable material to keep analysis, solutions, and communication consistent.
Control task scope and change radius so effort stays on what matters most.
Use tests, visual checks, and data validation to confirm the deliverable works.
Keep practical rollback paths for important changes and releases.
Capture effective methods as Skills, scripts, templates, and project assets.
I bring Skills, MCP, browsers, and specialist tools into real work, coordinating requirements, engineering, documentation, and verification to produce results that can be inspected and used.

AI PRACTICE / CONTINUOUS COLLABORATION
I avoid self-ratings and show real workflows, delivery scenarios, capability catalogs, and verification methods. Each item maps to a concrete action and usable output.
From goal clarification and execution to verification and learning
Engineering, project delivery, and knowledge engineering
Code, projects, documents, data, research, and QA
Builds, tests, rendering, and data checks
Callable capability units listed on this page
Runtime and knowledge context connections
These figures describe the current public workflow and catalog, not a rating, ranking, or external assessment.
Agent orchestration5-stage flow
Goals, context, roles, dependencies, and concurrencySkills design & reuse20-item catalog
Domain rules, templates, scripts, and acceptanceMCP & tool integration2 channels
Runtime tools and structured knowledge contextBrowser and desktop automationLive UI checks
Page operations, visible state, scripts, and visual acceptanceCode, docs, and data delivery3 delivery lanes
Engineering, documentation, tables, and visualizationVerification & review4 check types
Builds, tests, rendering, data validation, and issue closureFLOW / OPERATING MODEL
Define outcomes, constraints, and acceptance
PARALLEL DELIVERY LANES
From codebase discovery and architecture to implementation, testing, and deployment, keeping requirements, implementation, test results, and final behavior aligned.
Using AI for scope, tasks, schedule, risks, quality, and acceptance so project materials are more complete and traceable.
Turning project material and technical experience into searchable, reusable assets for RAG, engineering collaboration, and continuous delivery.
TOOLS / SKILLS / MCP
Twenty specialized capability units form the Skills layer, 12 cross-modal extensions form the tool layer, and two core connections form the MCP context layer. I combine them around each objective, connecting code, documents, data, browsers, and visual verification into one delivery chain.
Twenty callable capability units built from stable practice
Rules, templates, scripts, references, and acceptanceTwo core channels connecting runtime and knowledge
Structured context without repetitive copy and pasteTwelve cross-modal extensions for delivery
Code, documents, sheets, browsers, visuals, and contentRun independent work in parallel and integrate centrally
Useful for research, implementation, review, and comparisonOperate and validate real pages and local applications
DOM, screenshots, UI automation, local scriptsCombine local models, DeepSeek, and engineering services
Balancing cost, speed, data security, and controlPERSONAL AGENT PLATFORM / 20 + 12 + 2
Twenty Skills handle professional actions, 12 tool extensions provide cross-modal execution, and two MCP channels connect runtime and knowledge context. Together they support engineering, project delivery, content production, and quality assurance.
Extract goals, scope, constraints, and acceptance
Break complexity into tasks, dependencies, priorities, and milestones
Understand structure, debt, and impact
Implement Java, Python, and TypeScript outcomes
Improve local structure while preserving behavior
Design interfaces, schemas, errors, and integration notes
Clean, transform, batch, log, and isolate exceptions
Build parsing, retrieval, citations, evaluation, and governance
Design instructions, context, formats, and robustness tests
Coordinate roles, parallel tasks, context, and integration
Connect structured context and callable tools
Navigate, read, act, and validate visible state
Connect local apps, scripts, screenshots, and UI automation
Create requirements, designs, technical documentation, SOPs, and project reports
Organize data, formulas, charts, and checks
Use screenshots, rendering, and diffs for UI acceptance
Design relevant tests and explain failures
Identify security, access, quality, dependency, and delivery risks
Turn progress, issues, decisions, and outcomes into management views
Capture learning as Skills, templates, scripts, and next inputs
12 PLUGIN EXTENSIONS
2 MCP CONTEXT CHANNELS
Connects local execution, code, and engineering tools so an Agent can move from analysis to action.
Connects developer knowledge and structured professional context for stronger solutions and decisions.
APPLICATION SCENARIOS
Locate impact, implement incrementally, run relevant checks, and produce maintainable code and handoff.
Turn goals, scope, dependencies, risks, and acceptance into executable delivery structures.
Create and verify requirements, technical designs, project reports, SOPs, and knowledge documentation.
Handle sheets, logs, batch work, and repetitive flows with clear status, exception handling, and result checks.
Synthesize authoritative research, compare options, and produce clear recommendations.
Confirm delivery quality through builds, tests, screenshots, rendering, and diff checks.
QUALITY / GOVERNANCE
Clarify the problem and desired result so every Agent action supports delivery.
Use clear context and reliable material to keep analysis, solutions, and communication consistent.
Control task scope and change radius so effort stays on what matters most.
Use tests, visual checks, and data validation to confirm the deliverable works.
Keep practical rollback paths for important changes and releases.
Capture effective methods as Skills, scripts, templates, and project assets.
NEXT / ROLE FIT